Jiri Slaby fde5be353e HID: remove setup mutex, fix possible deadlock ... It causes recursive locking warning and is unneeded after introduction of STARTED flag. * Resume vs. stop is effectively solved by DISCONNECT flag. * No problem in suspend vs. start -- urb is submitted even after open which is possible after connect which is called after start. * Resume vs. start solved by STARTED flag. * Suspend vs. stop -- no problem in killing urb and timer twice. Reported-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Jiri Slaby <jirislaby@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>		2008-11-23 12:03:20 +01:00
..
hid-core.c	HID: remove setup mutex, fix possible deadlock	2008-11-23 12:03:20 +01:00
hid-pidff.c
hid-quirks.c
hiddev.c	saner FASYNC handling on file close	2008-11-01 09:49:46 -07:00
Kconfig
Makefile
usbhid.h	HID: remove setup mutex, fix possible deadlock	2008-11-23 12:03:20 +01:00
usbkbd.c	HID: remove warn() macro from usb hid drivers	2008-10-14 23:51:03 +02:00
usbmouse.c