| commit | b060da60bba7f8783d5df18efe7ef9b8957af69a | |
| author | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Sun, 19 Oct 2008 21:00:25 +0000 (19 19:00 -0200) | ||
| committer | Henrique de Moraes Holschuh <hmh@hmh.eng.br> | |
| Sun, 19 Oct 2008 21:01:27 +0000 (19 19:01 -0200) | ||
| tree | 58d0753408a1502748bef7b2559881084ad8fb5f | treesnapshot (tar.gz zip) |
| parent | ac36dc186a0e672ca229ff353dc83864fbc223bb | commitdiff |
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.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
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.
Signed-off-by: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ivo van Doorn <IvDoorn@gmail.com>
| net/rfkill/rfkill.c | diffblobblamehistory |