Hi,
On Wed, Mar 11, 2015 at 02:21:38AM +0200, Ruslan Bilovol wrote:
> >> @@ -469,6 +488,16 @@ int usb_gadget_unregister_driver(struct
> >> usb_gadget_driver *driver)
> >> break;
> >> }
> >>
> >> + if (ret) {
> >> + struct usb_gadget_driver
On Wed, 11 Mar 2015, Ruslan Bilovol wrote:
> Hi Alan,
Hello.
> > If you add the list_init and list_del_init above, this loop won't be
> > needed. You can just call list_del.
>
> I disagree with this. This function is externally visible and we can't
> guarantee that some buggy code will not
Hi Alan,
On Tue, Feb 17, 2015 at 11:51 PM, Alan Stern wrote:
> On Tue, 17 Feb 2015, Ruslan Bilovol wrote:
>
>> Change behavior during registration of gadgets and
>> gadget drivers in udc-core. Instead of previous
>> approach when for successful probe of usb gadget driver
>> at least one usb
Hi,
On Wed, Mar 11, 2015 at 02:21:38AM +0200, Ruslan Bilovol wrote:
@@ -469,6 +488,16 @@ int usb_gadget_unregister_driver(struct
usb_gadget_driver *driver)
break;
}
+ if (ret) {
+ struct usb_gadget_driver *tmp;
+
+
On Wed, 11 Mar 2015, Ruslan Bilovol wrote:
Hi Alan,
Hello.
If you add the list_init and list_del_init above, this loop won't be
needed. You can just call list_del.
I disagree with this. This function is externally visible and we can't
guarantee that some buggy code will not call it
Hi Alan,
On Tue, Feb 17, 2015 at 11:51 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 17 Feb 2015, Ruslan Bilovol wrote:
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at
On Tue, 17 Feb 2015, Ruslan Bilovol wrote:
> Change behavior during registration of gadgets and
> gadget drivers in udc-core. Instead of previous
> approach when for successful probe of usb gadget driver
> at least one usb gadget should be already registered
> use another one where gadget drivers
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and gadgets
can be registered in udc-core
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and gadgets
can be registered in udc-core
On Tue, 17 Feb 2015, Ruslan Bilovol wrote:
Change behavior during registration of gadgets and
gadget drivers in udc-core. Instead of previous
approach when for successful probe of usb gadget driver
at least one usb gadget should be already registered
use another one where gadget drivers and
10 matches
Mail list logo
