Okay, in a separate thread on LKML Andrew Morton has said he doesn't
really like my approach either. Then what should it be?
Clumsily use different routines for locking the first vs. the
others in a nested set? (Or clumsily force drivers that want
to lock more than one device to explicitly acquire and release
the readlock?)
Or only allow one thread to lock a USB device at any time?
(That is, don't lock individual devices but only lock the
entire set of USB devices.)
Having already made a choice that so many people dislike, I feel certain
that no matter which one I pick it will turn out to be the wrong one. So
I'll wait to hear from everyone else. Suggestions for other alternatives
beyond these two would be nice.
Alan Stern
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
