that and lack any ability to have separate timeouts.
As far as mass-storage is concerned, USB is merely a transport. It
doesn't impose any timeout rules; the appropriate timeout value is
whatever the device at the end of the USB link needs. Thus, a SCSI
drive connected over USB could use
_head, *xa_head2;
This is an idiom specifically intended to reduce the likelihood of
errors. Rather like avoiding assignments inside conditionals.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ass. The tree of struct devices, each with
its own lock, gets used in many different and complicated ways.
Lockdep can't understand this -- it doesn't have the ability to
represent an arbitrarily deep hierarchical tree of locks -- so we tell
it to ignore the device locks.
It
h driver is to blame (uas, btrfs, or xhci).
Does this happen with usb-storage instead of uas?
What about with ehci-hcd instead of xhci-hcd?
And just to be exotic, what about with dummy-hcd and the uas or
g_mass_storage gadget driver?
Alan Stern
--
To unsubscribe from this list: send the l
