On Wed, 29 Jan 2003, David Brownell wrote: > Hi, > > > Even worse is the fact that -EBUSY has a dual meaning: along with > > indicating that the urb has already started to finish up, it also can mean > > that the urb was not active in the first place -- i.e., had already > > completed by the time usb_unlink_urb was called, or had never been > > submitted at all. > > I don't think so, unless the device driver is playing with urb->hcpriv. > > The "already completed" case is currently flagged by that being null, > so unlink returns -EINVAL; leaving the -EBUSY case as indicating only > the "starting to complete" case.
I wish I had known that before. It means my proposed patch for synchronous unlinks is wrong. *Sigh* Back to the drawing board. Alan Stern ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
