> > > > The HCD is most _certainly_ allowed to block when cleaning up > > > > device state. Every device management API I've had reason to > > > > look at in Linux guarantees that the the "clean up after this device" > > > > call can block. > > > > > > You haven't been looking hard enough. Take a look at all of the > > > networking code. > > > > You mean like unregister_netdev()? Which is guaranteed > > to call net->stop() in a thread context? Sorry, I know that one. > > It almost seems like you're trying to be stubborn or difficult. The > world is not just devices.
That's why I specified device management, where the kernel is keeping its data structures in sync with the hardware that's actually present. Talking to hardware often means you need to block ... part of my point. I'm not sure why you think that having supporting evidence for a statement I make would be "stubborn" or "difficult". - Dave _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
