Hi,
On 07-06-16 17:18, Alan Stern wrote:
On Tue, 7 Jun 2016, Hans de Goede wrote:
Hi,
On 06-06-16 19:03, Alan Stern wrote:
On Mon, 6 Jun 2016, Hans de Goede wrote:
Hi,
On 06-06-16 16:48, Greg Kroah-Hartman wrote:
On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
Hi All,
Wh
On Tue, 7 Jun 2016, Hans de Goede wrote:
> Hi,
>
> On 06-06-16 19:03, Alan Stern wrote:
> > On Mon, 6 Jun 2016, Hans de Goede wrote:
> >
> >> Hi,
> >>
> >> On 06-06-16 16:48, Greg Kroah-Hartman wrote:
> >>> On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
> Hi All,
>
> >>>
Hi,
On 06-06-16 19:03, Alan Stern wrote:
On Mon, 6 Jun 2016, Hans de Goede wrote:
Hi,
On 06-06-16 16:48, Greg Kroah-Hartman wrote:
On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
Hi All,
While looking at libusb today I ended up looking at the
reap-after-disconnect code.
Wha
On Mon, 6 Jun 2016, Hans de Goede wrote:
> Hi,
>
> On 06-06-16 16:48, Greg Kroah-Hartman wrote:
> > On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
> >> Hi All,
> >>
> >> While looking at libusb today I ended up looking at the
> >> reap-after-disconnect code.
> >>
> >> What stands
Hi,
On 06-06-16 16:48, Greg Kroah-Hartman wrote:
On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
Hi All,
While looking at libusb today I ended up looking at the
reap-after-disconnect code.
What stands out is that libusb expects to be able to
reap all outstanding urbs on a devic
On Mon, Jun 06, 2016 at 01:44:23PM +0200, Hans de Goede wrote:
> Hi All,
>
> While looking at libusb today I ended up looking at the
> reap-after-disconnect code.
>
> What stands out is that libusb expects to be able to
> reap all outstanding urbs on a device on receiving
> a POLL_ERR status from
