similar to: ARC target support for jumps with LImm

The script queries **all** issues with specified labels and "notifies" on each of those. While this approach works, I doubt it would scale well if everyone is doing this by hand. OTOH, building a service that does this for everyone might be feasible, albeit non-trivial and it's not clear who should own this. So overall having this supported by GitHub would mean a much better UX...

Well, it's not really critical for us _now_, because we have not switched to github issues. And I can't really see any possibility of that happening in the short-term, either. Even once we do decide we want to move that way -- which we haven't yet even done -- it'll be a long road to making it happen, and I suspect there's many more critical missing features that we'll

On Sun, Oct 29, 2017 at 02:34:56PM +0000, Ilya Lesokhin wrote: > > -----Original Message----- > > From: Michael S. Tsirkin [mailto:mst at redhat.com] > > Sent: Sunday, October 29, 2017 4:22 PM > > To: Ilya Lesokhin <ilyal at mellanox.com> > > Cc: virtio-dev at lists.oasis-open.org; virtualization at lists.linux-foundation.org > > Subject: Re: packed ring

On Sun, Oct 29, 2017 at 02:34:56PM +0000, Ilya Lesokhin wrote: > > -----Original Message----- > > From: Michael S. Tsirkin [mailto:mst at redhat.com] > > Sent: Sunday, October 29, 2017 4:22 PM > > To: Ilya Lesokhin <ilyal at mellanox.com> > > Cc: virtio-dev at lists.oasis-open.org; virtualization at lists.linux-foundation.org > > Subject: Re: packed ring

If you do this whats the point of the id? Just use descriptor offset like virtio 0 did. On Sun, Oct 29, 2017 at 09:05:01AM +0000, Ilya Lesokhin wrote: > My point was that if the driver is not required to change the IDs, > it can initialized the ID's in all the descriptors when the ring is created > and never write the ID field again. > > A simple allocator for the IDs can

If you do this whats the point of the id? Just use descriptor offset like virtio 0 did. On Sun, Oct 29, 2017 at 09:05:01AM +0000, Ilya Lesokhin wrote: > My point was that if the driver is not required to change the IDs, > it can initialized the ID's in all the descriptors when the ring is created > and never write the ID field again. > > A simple allocator for the IDs can

On Sun, Oct 08, 2017 at 06:16:44AM +0000, Ilya Lesokhin wrote: > > > -----Original Message----- > > > From: virtualization-bounces at lists.linux-foundation.org > > > [mailto:virtualization-bounces at lists.linux-foundation.org] On Behalf > > > Of Michael S. Tsirkin > > > > > > This is an update from v2 version. > >> ... > > >

On Sun, Oct 08, 2017 at 06:16:44AM +0000, Ilya Lesokhin wrote: > > > -----Original Message----- > > > From: virtualization-bounces at lists.linux-foundation.org > > > [mailto:virtualization-bounces at lists.linux-foundation.org] On Behalf > > > Of Michael S. Tsirkin > > > > > > This is an update from v2 version. > >> ... > > >

Hey, Ferret is repeatedly seg-faulting my mongrel servers on the same line: /usr/local/lib/ruby/gems/1.8/gems/ferret-0.10.11/lib/ferret/index.rb:718: [BUG] Segmentation fault ruby 1.8.5 (2006-08-25) [i686-linux] I''m using ferret 0.10.11. I haven''t had the time to dig into yet, it''s on the backburner right now - I just keep several spare servers and restart them

was "nv50/ir: PostRaConstantFolding improvements" before. nothing really changed from the last version, just minor things. Karol Herbst (5): nv50/ir: restructure and rename postraconstantfolding pass nv50/ir: implement mad post ra folding for nvc0+ gk110/ir: add LIMM form of mad gm107/ir: add LIMM form of mad nv50/ir: also do PostRaLoadPropagation for FMA

Dear Arun, I am a novice in R bu some my friends that use R for a long time were not able to help me. Thank you really. Concerning your question why I need it, I think that it can be situations where the condition, that I have to apply, depends on the data. May be you can advice me a good text to learn programming in R. Thank you again. Ilya Novikov Sat, Jan 19, 2013 at 8:02 PM, arun kirshna [via

On Tue, Jan 15, 2019 at 1:47 PM Chandler Carruth <chandlerc at gmail.com> wrote: > Has anyone reached out to GitHub about potentially enabling this? > For the lack of a better place, filed a ticker against GitHub support. Will update the thread when they come back to me. -- Regards, Ilya Biryukov -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Thu, Nov 02, 2017 at 11:40:36AM +0000, Ilya Lesokhin wrote: > Hi, > I've noticed that the virtio-net uses skb->cb. > > I don't know all the detail by my understanding is it caused problem with the mlx5 driver > and was fixed here: > https://github.com/torvalds/linux/commit/34802a42b3528b0e18ea4517c8b23e1214a09332 > > Thanks, > Ilya Thanks a lot for the

On Thu, Nov 02, 2017 at 11:40:36AM +0000, Ilya Lesokhin wrote: > Hi, > I've noticed that the virtio-net uses skb->cb. > > I don't know all the detail by my understanding is it caused problem with the mlx5 driver > and was fixed here: > https://github.com/torvalds/linux/commit/34802a42b3528b0e18ea4517c8b23e1214a09332 > > Thanks, > Ilya Thanks a lot for the

Hello developers, I have a question about supported bitrates for SPEEX. Regardless of whether I specify a 10kbps or a 8kbps bitrate, the encoded .spx file is the same size and have the same PESQ value. This makes me wonder if SPEEX supports arbitrary bitrates, or only a certain set. A few more details about my configuration: I am using SPEEX encoder version 1.1.12 I am encoding a narrowband

A bunch of fixes (memory leaks, NULL pointer dereferences and devices hanging in busy state) to sanitize error handling during mount sequence. This is on top of for-linus + slyfox''s double-free fix. Thanks, Ilya Ilya Dryomov (5): Btrfs: fix memory leak in btrfs_parse_early_options() Btrfs: fix subvol_name leak on error in btrfs_mount() Btrfs: avoid null dereference and leaks

Hi, folks! There is FreeBSD 7.1, NUT 2.4.1, UPS APC Smart 2200 XL. NUT is compiled from ports with following options: --------------------------------------- _OPTIONS_READ=nut-2.4.1_5 WITH_SERIAL=true WITH_USB=true WITH_SNMP=true WITHOUT_NEON=true WITHOUT_PDU=true WITHOUT_HAL=true WITHOUT_IPV6=true WITHOUT_CGI=true --------------------------------------- UPS is successfully recognized by OS

Hello Developers, I am considering using SPEEX on an embedded processor that does not have a floating point unit. Does anybody have a SPEEX performance characterization on a fixed point processor? More specifically, I am interested in knowing how the MFLOPS values from Table 9.2 in the manual translate to fixed-point instructions when SPEEX is compiled with enable-fixed-point option. Any help

Hello! I hope, i'm doing right, writing here. I have a question about the R statistical formulas: were can I look, what are they? E. g. I'd like to know which exactly mathematical formula is used in Wilcoxon test, and others. Is there somewhere on the Internet information about that? Thanks a lot! Ilya. PS Sorry for any mistakes in my English, it is not my mother-tongue.

Hi. I have the same problem, which described in: http://lists.xensource.com/archives/html/xen-users/2010-07/msg00241.html I''m using Debian Squeeze (2.6.32-5-xen-amd64) in Dom0, Xen 4.0.1-rc6, Windows 2008, 2003 x86_64 in domU After installing drivers from http://www.xen.org/files/XenCloud/Software/0.5/XCP-base-0.5.iso, system stops on progress bar in normal boot, but ok in safe mode. In