Hi, I am interested to the understand the design decisions for changing from tasklets to workqueues. Was there a fundamental flaw that necessitated the change ? I am asking because I am getting a Bluetooth "scheduling while atomic" failure on an ARM based 2.6.34 kernel (with some 2.6.37 Bluez backports). Changing to workqueues would avoid this issue as a workqueue use process context that can sleep. Thanks for any info on the design decisions. Regards, Dean -- 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
