Henrique de Moraes Holschuh 417bd25ac4 rfkill: update LEDs for all state changes ... The LED state was not being updated by rfkill_force_state(), which will cause regressions in wireless drivers that had old-style rfkill support and are updated to use rfkill_force_state(). The LED state was not being updated when a change was detected through the rfkill->get_state() hook, either. Move the LED trigger update calls into notify_rfkill_state_change(), where it should have been in the first place. This takes care of both issues above. Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br> Acked-by: Ivo van Doorn <IvDoorn@gmail.com> Cc: stable@kernel.org Signed-off-by: John W. Linville <linville@tuxdriver.com>		2008-10-06 18:14:57 -04:00
..
Kconfig	[RFKILL]: Add support for an rfkill LED.	2007-10-10 16:54:10 -07:00
Makefile
rfkill-input.c	rfkill: query EV_SW states when rfkill-input (re)?connects to a input device	2008-08-01 15:31:32 -04:00
rfkill-input.h	rfkill: add default global states (v2)	2008-08-22 16:29:56 -04:00
rfkill.c	rfkill: update LEDs for all state changes	2008-10-06 18:14:57 -04:00