On Sun, 22 Jan 2012, Keith Packard wrote: > Ok, so this is a comedy of errors. The Bluetooth code is trying to use > an iso-specific flag (URB_ISO_ASAP) on a bulk endpoint, which is > invalid, but normally harmless. Unless the USB code is compiled for > debugging, in which case it checks a bunch for incorrect usage and > discards URBs which are wrong. > > As far as I'm concerned, #ifdef DEBUG code should never ever change > the behaviour of the code, and so I'd say the USB code is even more > broken than the bluetooth code... Well, if the DEBUG code never changed any behaviors at all, it would be pretty useless, wouldn't it? In this case, the change in behavior involves printing out a kernel message announcing a bug. Causing the submission to fail also helps draw people's attention to the bug. Under the circumstances, I think this is understandable and not truly broken. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
