> In that other driver structure, synchronizing on urb completions > after an (async) unlink failure would either (a) have succeeded, > because the "failure" was like the EBUSY case, "warp crystals > would explode if we unlinked any faster", or (b) failed because > of some HCD problem. > > Success means all is fine; failure (b) would be khubd hanging. > Annoying (reboot to recover, no more modprobes) but 100% safe.
OK, maybe we have been talking at cross-purposes then, since I have been doing it this way (waiting for urb completion) since the beginning (speedtouch.c). By the way, is there any advantage to doing an async unlink rather than a synchronous one in this situation? Thanks, Duncan. ------------------------------------------------------- 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
