Henrique de Moraes Holschuh 95a3690291 rfkill: update LEDs for all state changes ... commit 417bd25ac4 upstream 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> Signed-off-by: John W. Linville <linville@tuxdriver.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>		2008-10-18 10:49:12 -07:00
..
Kconfig	[RFKILL]: Add support for an rfkill LED.	2007-10-10 16:54:10 -07:00
Makefile	[NET]: rfkill: add support for input key to control wireless radio	2007-05-07 00:34:20 -07:00
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: do not allow userspace to override ALL RADIOS OFF	2008-06-26 14:21:22 -04:00
rfkill.c	rfkill: update LEDs for all state changes	2008-10-18 10:49:12 -07:00