I realize it's not all your doing, but that's an EVENT not a state flag, But you're treating it as a state flag. (Like the original somewhat goofy 69ee472f2706371ca639de49b06df91615c07d8d from Oliver). Even as a flag, its semantics seem fuzzy... like they should be covered by other state in the network and/or power management stacks. I'd like to see this botch fixed, not worsened. Maybe you and Oliver could collaborate on fixing it, and getting other state flags out ofthe word used to track and signal events? If you've ever worked with hardware that makes that kind of mistake, you know how error-prone it is ... Meanwhile, NAK. ISTR related Comments came up when a previous incarnation of this patch circulated, from at least Alan Stern. What happened to that? Events trigger state transitions and similar actions. So A "leave sleep state" event" might be a place to trigger RX urb insertion as part of wake-up processing. (Ideally, there'd be no need to set an event bit to trigger it as deferred work ... the reason to have a word of event bits for some other events. -- 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
