> > Conclusion B: you must loop around retrying usb_unlink_urb until it > > succeeds (if ever). Is that right? > > If usb_unlink_urb() actually fails, I truly doubt that it will ever > succeed. So retrying is not likely to help at all. On the other hand, > maybe it's not so bad to just sit around and wait in disconnect() for the > completion handler to be called. You would end up blocking the khubd > thread and the unload process, but that's better than crashing the kernel.
That is what I do right now (speedtouch.c). 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
