diff options
author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | 2008-10-03 16:58:05 -0300 |
---|---|---|
committer | John W. Linville <linville@tuxdriver.com> | 2008-10-06 18:14:57 -0400 |
commit | 417bd25ac4c6f76c8aafe8a584f3620f4a936b72 (patch) | |
tree | 7b7b55d715d7121dcba815cd2518608c0a6ec010 /lib/locking-selftest-mutex.h | |
parent | 5b5d13afeeee959a74114b73c560d3e243f34a11 (diff) |
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>
Diffstat (limited to 'lib/locking-selftest-mutex.h')
0 files changed, 0 insertions, 0 deletions