Am Mittwoch, 13. Juni 2007 schrieb Alan Stern:
> IMO the fine distinctions above simply don't matter. Drivers don't
> care anyway, since they can't know what stage the URB is at when they
> try to unlink it.
>
> The only possible place where this might matter is in usbtest, which
> specifically intends to test the unlink code paths. Even there,
> I'm not sure that usb_unlink_urb needs to return a meaningful value;
> the URB's final status code ought to be sufficient.
>
> So -- is there any objection if I change usb_unlink_urb to return void?
As far as I am concerned, change it to void.
Regards
Oliver
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
