On Wed, 7 Apr 2010, Jason Wessel wrote: > > (Although in this case, it looks like the problem has an easy fix.) > > > > > What kind of easy fix did you have in mind Alan? Changing the test between the usb_submit_urb() call and the dev_err() statement. > Previously I shuffled around the error messages to avoid this problem > with one of the drivers, but that is definitely not the right fix, as it > only fixes a single driver. I don't think there's any other way to do it. The tests and error messages are different in each driver; ideally they should all be changed to the same thing. > I have not looked at this code in a while, > but I believe the right fix is to look for the connected condition in > the usb serial console high level console code, as well as to simply > have a recursion check. Or just not to print error messages when URBs can't be sumbitted because the disconnect routine was called. > Certainly, there are several ways the problem could be addressed. Alan Stern -- 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
