On Wednesday 07 June 2006 6:38 am, Andrew Morton wrote: > > Oh my...
Minor issue that can only cause trouble if the last port gets an overcurrent indication (an uncommon hardware fault) ... the variable is only tested once after it's potentially clobbered, while the potential clobber is on a code path that only triggers with the experimental USB_SUSPEND config option. AFAIK nobody yet relies on that option; too many USB drivers still have broken suspend() or resume() methods to rely on it. So, worth fixing but not sweating over. > one can see that code has been added trying to cope > with problem caused by using same variable for different things. Not so. _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
