Hi, Quick question that will save a lot of time slogging through usbcore code if someone will indulge me. Is it necessary to kill all outstanding urbs in a driver's disconnect function? I've seen documentation saying that the usbcore takes care of this when the disconnect is detected, suggesting that tracking outstanding urbs and killing them in the driver's disconnect function is unnecessary. But I also see drivers that do just that. As I understand it, an urb killed by usbcore will have its callback invoked, with the result code indicating that it was killed, which the callback can handle gracefully. Any errors in my understanding? Thanks everyone! Mike ---- -- 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
