Mitigation for those with floods of: Bluetooth: Unexpected Continuation Frame (len 0) in their logs. The underlying cause of this is still far from crystal clear (at least, not to me), but, anyhow, I'm sold on Marcel's advice to solve this by placing my dongle in the garbage. Previously I suggested dropping the printk entirely but ratelimiting is better, since the printk is not wrong (or, if it were wrong, this would at least be indicative of a problem elsewhere). -- 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
