On Wed, Nov 06, 2013 at 12:27:21PM -0800, Julius Werner wrote: > This patch adds a check for USB_STATE_NOTATTACHED to the > hub_port_warm_reset_required() workaround for ports that end up in > Compliance Mode in hub_events() when trying to decide which reset > function to use. Trying to call usb_reset_device() with a NOTATTACHED > device will just fail and leave the port broken.
Who makes those calls, drivers? Any specific ones that you know need to be fixed? > Also bumped the messages about this kind of reset failure from dev_dbg() > to dev_warn() to make it easier to notice, since calling that function > with a NOTATTACHED device would almost always be a bug But what can a user do if those messages show up? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
