How about this one instead?
Introduce unlocked version of usb_set_configuration: __usb_set_configuration.
That'd work too ... but it assumes that long term we'd want to keep both versions. Do we really need to do that?
Seems to me there's no reason any device driver should use either one of those calls. (They have usb_reset_config for the typical "light reset" functionality.) And that all of usbcore should probably be using the unlocked version ...
- Dave
------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
