If you need to have disconnect() called in all cases, feel free to get rid of usb_interface.driver ... it needs to go someday, and I'd guess that's making trouble for you.
I'm happy to get rid of it... but I don't really want my usbfs fix to change behaviour for other drivers.
When I looked it it, usbfs was the only code I was certain would be affected by that change. It was one of those moments where I scratched my head and asked "How could that ever have worked correctly?" ...
I can't see the CDC (ACM, Ethernet) or audio (ALSA, OSS) drivers getting into trouble with that any time soon, but those are the only other users of the claim/release calls righ now.
I don't have any way of testing most of those.
Because of when the interfaces are released, it's not likely they'll have problems. But I can test a couple of them to make sure that's the case, once your patch is ready. If any problems do come up, the fixes wouldn't be hard.
- Dave
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
