On 16.08.2017 18:24, Alan Stern wrote:
> On Wed, 16 Aug 2017, Alexey Khoroshilov wrote:
>
>> Hello,
>>
>> usb_add_gadget_udc_release() gets release() argument that allows to
>> release user resources.
>>
>> As far as I can see, the release() is called on error paths
>> of
On 16.08.2017 18:24, Alan Stern wrote:
> On Wed, 16 Aug 2017, Alexey Khoroshilov wrote:
>
>> Hello,
>>
>> usb_add_gadget_udc_release() gets release() argument that allows to
>> release user resources.
>>
>> As far as I can see, the release() is called on error paths
>> of
On Wed, 16 Aug 2017, Alexey Khoroshilov wrote:
> Hello,
>
> usb_add_gadget_udc_release() gets release() argument that allows to
> release user resources.
>
> As far as I can see, the release() is called on error paths
> of usb_add_gadget_udc_release() as a result of
> put_device(>dev);
>
On Wed, 16 Aug 2017, Alexey Khoroshilov wrote:
> Hello,
>
> usb_add_gadget_udc_release() gets release() argument that allows to
> release user resources.
>
> As far as I can see, the release() is called on error paths
> of usb_add_gadget_udc_release() as a result of
> put_device(>dev);
>
Hi,
Alexey Khoroshilov writes:
> Hello,
>
> usb_add_gadget_udc_release() gets release() argument that allows to
> release user resources.
>
> As far as I can see, the release() is called on error paths
> of usb_add_gadget_udc_release() as a result of
> put_device(>dev);
Hi,
Alexey Khoroshilov writes:
> Hello,
>
> usb_add_gadget_udc_release() gets release() argument that allows to
> release user resources.
>
> As far as I can see, the release() is called on error paths
> of usb_add_gadget_udc_release() as a result of
> put_device(>dev);
> except for the only
Hello,
usb_add_gadget_udc_release() gets release() argument that allows to
release user resources.
As far as I can see, the release() is called on error paths
of usb_add_gadget_udc_release() as a result of
put_device(>dev);
except for the only path going via err1.
As a result a caller of the
Hello,
usb_add_gadget_udc_release() gets release() argument that allows to
release user resources.
As far as I can see, the release() is called on error paths
of usb_add_gadget_udc_release() as a result of
put_device(>dev);
except for the only path going via err1.
As a result a caller of the
8 matches
Mail list logo