* This can be used by drivers to release an interface without waiting * for their disconnect() methods to be called. It causes disconnect * to be called, except possibly when used from a probe() method.
But that's not the only case when it wouldn't be called.
What other cases are there?
Any release_interface() after the the initial probe() succeeded, and before the device_add() is issued. That's not necessarily in a probe() method. Plus there are physical disconnect paths that are probably going to need revisiting at some point, given a 2.4-ish "disconnect while probing" message I saw recently.
- Dave
My own experience in specifying APIs suggests to me rather strongly that these oddball cases aren't worth nailing down in natural language at this time.
- Dave
Duncan.
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
