Maksim Yevmenkin 82e1becc5f Fix dangling callout problem in the Bluetooth L2CAP code that leads to ... panic. The panic happens when outgoing L2CAP connection descriptor is deleted with the L2CAP command(s) pending in the queue. In this case when the last L2CAP command is deleted (due to cleanup) and reference counter for the L2CAP connection goes down to zero the auto disconnect timeout is incorrectly set. pjd gets credit for tracking this down and committing bandaid. Reported by: Jonatan B <onatan at gmail dot com> MFC after: 3 days		2005-08-31 18:13:23 +00:00
..
common	Change the embedded module name from "bluetooth" to "ng_bluetooth" to match	2005-04-08 05:13:53 +00:00
drivers	Ignore AVM BlueFRITZ! USB Bluetooth Adapter v1.0 (product ID 0x2200).	2005-07-19 00:33:37 +00:00
hci	/* -> /*- for license, minor formatting changes	2005-01-07 01:45:51 +00:00
include	Fix dangling callout problem in the Bluetooth L2CAP code that leads to	2005-08-31 18:13:23 +00:00
l2cap	Fix dangling callout problem in the Bluetooth L2CAP code that leads to	2005-08-31 18:13:23 +00:00
socket	Fix multiple typos in the mutex names. This fixes false positive (and pretty	2005-08-23 00:50:59 +00:00