| commit | fe643414dbf330d6d910e01edd48dd93dc6f2942 | |
| author | Jiri Slaby <jirislaby@gmail.com> | |
| Tue, 14 Jul 2009 20:37:13 +0000 (14 22:37 +0200) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Fri, 24 Jul 2009 19:05:14 +0000 (24 15:05 -0400) | ||
| tree | a4db7f0290aad3541da254dc3f5e287a5c733e25 | treesnapshot (tar.gz zip) |
| parent | a94ca4e7af0e6b63ef5345750fad8e1400274ba4 | commitdiff |
wireless: wl12xx, fix lock imbalance
Add omitted mutex_unlock to one of wl12xx_op_start fail paths (when
wl12xx_chip_wakeup fails).
[v2]
Power off the device, because:
\= cite from http://marc.info/?l=linux-kernel&m=124755028209880&w=2
If the chip cannot be booted, why should it remain powered on?
In some rare cases, the chip might fail to initialize, but can
recover if powered off and on again, so turning it off at this
point is the right thing to do. =/
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Add omitted mutex_unlock to one of wl12xx_op_start fail paths (when
wl12xx_chip_wakeup fails).
[v2]
Power off the device, because:
\= cite from http://marc.info/?l=linux-kernel&m=124755028209880&w=2
If the chip cannot be booted, why should it remain powered on?
In some rare cases, the chip might fail to initialize, but can
recover if powered off and on again, so turning it off at this
point is the right thing to do. =/
Signed-off-by: Jiri Slaby <jirislaby@gmail.com>
Reviewed-by: Luciano Coelho <luciano.coelho@nokia.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/wl12xx/wl1251_main.c | diffblobblamehistory |