hi Greg and Sergei:
>Well, I didn't want to complain about the example patch but now I'll just
> have to... :-)
>
>
>> Here it is
>
>> diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
>> index 090469e..2192776 100644
>> --- a/drivers/usb/core/hub.c
>> +++ b/drivers/usb/core/hub.c
Hello.
On 04/13/2014 06:06 PM, vichy wrote:
Allways run your patches through checkpatch.pl so someone doesn't point
out the formatting issues in it when you send it to the mailing list :)
Well, I didn't want to complain about the example patch but now I'll just
have to... :-)
Here it i
On Sun, Apr 13, 2014 at 10:06:15PM +0800, vichy wrote:
> hi Greg:
>
> > Allways run your patches through checkpatch.pl so someone doesn't point
> > out the formatting issues in it when you send it to the mailing list :)
> Here it is
You didn't actually use checkpatch.pl :(
--
To unsubscribe from
hi Greg:
> Allways run your patches through checkpatch.pl so someone doesn't point
> out the formatting issues in it when you send it to the mailing list :)
Here it is
diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c
index 090469e..2192776 100644
--- a/drivers/usb/core/hub.c
+++ b/dri
On Sun, Apr 13, 2014 at 03:43:47PM +0800, vichy wrote:
> hi all:
> When I plug in usb3.0 device for stressing test, once
> usb_get_device_descriptor fail in hub_port_init.
> we will call hub_port_disable(hub, port1, 0);
>
> And usb3.0 device may not recover successfully only with below function
>
hi all:
When I plug in usb3.0 device for stressing test, once
usb_get_device_descriptor fail in hub_port_init.
we will call hub_port_disable(hub, port1, 0);
And usb3.0 device may not recover successfully only with below function
retval = hub_port_reset(hub, port1, udev, delay, false);
when we
