Re: [umap2] status of issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2 Sep 2016, Binyamin Sharet (bsharet) wrote:

> 
> > On 2 Sep 2016, at 15:31, Greg KH <greg@xxxxxxxxx> wrote:
> > 
> > On Fri, Sep 02, 2016 at 12:09:40PM +0000, 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 reproduced means - not reproduced on 4.7 and 4.8-rc2.
> >> 
> >> The issues appear with the same numbering as in the detailed emails.
> >> 
> >> [01/11][0aa8:8001] not reproduced
> >> [02/11][10cf:5500] reproduced, no patch provided
> >> [03/11][0471:0602] not reproduced
> >> [04/11][0557:2002] reproduced (happens when FW is missing)
> >>                  fixed in a patch I received from Oliver Neukum
> >> [05/11][22b8:2d93] not reproduced
> >>                  fixed for v4.4 (which has this issue) in patches I received from Oliver
> >> [06/11][3923:718a] reproduced, no patch provided
> >> [07/11][160a:3184] reproduced, no patch provided
> >> [08/11][076d:0006] not reproduced
> >> [09/11][05c5:0002] not reproduced
> >> [10/11][1a0a:0102] not a bug. expected behaviour.
> >> [11/11][9022:d483] reproduced.
> >>                  after testing a patch from Felipe, we moved to a new issue, no patch for it yet.
> >> 
> > 
> > I have no idea how to track these xxxx:xxxx values back to a driver
> > easily, can you give me a hint?
> > 
> > Think about someone receiving this type of message, it's a bit hard to
> > know what needs to be done here, right?
> > 
> > still confused.
> > 
> > greg k-h
> 
> Sorry for the confusion.
> 
> Each one of the issues was reported in a separate mail, detailing the source
> file which registered to this VID/PID. (the mail subjects are [Umap2][x/11][vid:pid])
> 
> Here are the sources of the issues that were reproduced:
> 
> [02/11][10cf:5500] drivers/staging/comedi/drivers/vmk80xx.c
> [04/11][0557:2002] drivers/net/usb/kaweth.c
> [06/11][3923:718a] drivers/staging/comedi/drivers/ni_usb6501.c
> [07/11][160a:3184] drivers/staging/vt6656/main_usb.c (related: drivers/staging/comedi/drivers/usbduxsigma.c)
> [11/11][9022:d483] drivers/media/usb/dvb-usb/dw2102.c

The problem with kaweth has been fixed by Oliver's patch.  The dvb-usb 
problem is unlikely to be fixed until one of the DVB maintainers looks 
at it.

And all the other unresolved problems involve drivers in the staging 
directory, which aren't expected to be in very good shape anyway.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux