On Sunday 18 January 2009, Oliver Neukum wrote: > Am Saturday 17 January 2009 23:44:12 schrieb David Brownell: > > > Do you know which HCDs are affected? > > > > The unlinking issue generally applies to any HCD that > > doesn't have to disable hardware queues to unlink. > > It's the "disable queue" which forces a contex switch > > on stuff like EHCI/OHCI/UHCI, so they don't see $SUBJECT. > > Or alternatively, we make sue the status given to the completion > handler must be used to decide which form of locking is appropriate > to use. On second thought that seems the most elegant solution > to me. This must be some new definition of "elegant" that I've not previously come across... I've heard of language evolving over time, but this seems extreme! The general policy with locking is that a given procedure should always work the same. If there are two different locking policies, there should be two different entry points. - Dave -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
