Re: [umap2] status of issues

2016-09-26 Thread Oliver Neukum
On Fri, 2016-09-02 at 12:41 +, Binyamin Sharet (bsharet) wrote: > Hi, > Here are the sources of the issues that were reproduced: so it seems to me that the current state is: > [02/11][10cf:5500] drivers/staging/comedi/drivers/vmk80xx.c open > [04/11][0557:2002] drivers/net/usb/kaweth.c fi

Re: [umap2] status of issues

2016-09-02 Thread Alan Stern
On Fri, 2 Sep 2016, Binyamin Sharet (bsharet) wrote: > > > On 2 Sep 2016, at 15:31, Greg KH wrote: > > > > On Fri, Sep 02, 2016 at 12:09:40PM +, Binyamin Sharet (bsharet) wrote: > >> Hi, > >> > >> After confusing Greg, here’s the current status of all 11 issues initially > >> reported by

Re: [umap2] status of issues

2016-09-02 Thread Binyamin Sharet (bsharet)
> On 2 Sep 2016, at 15:31, Greg KH wrote: > > On Fri, Sep 02, 2016 at 12:09:40PM +, Binyamin Sharet (bsharet) wrote: >> Hi, >> >> After confusing Greg, here’s the current status of all 11 issues initially >> reported by us. >> >> Since the initial tests were done on a rather old kernel (4

Re: [umap2] status of issues

2016-09-02 Thread Greg KH
On Fri, Sep 02, 2016 at 12:09:40PM +, Binyamin Sharet (bsharet) wrote: > Hi, > > After confusing Greg, here’s the current status of all 11 issues initially > reported by us. > > Since the initial tests were done on a rather old kernel (4.4) we retested on > 4.7 and 4.8-rc2, > so, not reprod

[umap2] status of issues

2016-09-02 Thread Binyamin Sharet (bsharet)
Hi, After confusing Greg, here’s the current status of all 11 issues initially reported by us. Since the initial tests were done on a rather old kernel (4.4) we retested on 4.7 and 4.8-rc2, so, not reproduced means - not reproduced on 4.7 and 4.8-rc2. The issues appear with the same numbering