summaryrefslogtreecommitdiffstats
path: root/MAINTAINERS
diff options
context:
space:
mode:
authorStanislaw Gruszka2010-12-23 12:38:21 +0100
committerJohn W. Linville2011-01-04 20:15:08 +0100
commit554d1d027b19265c4aa3f718b3126d2b86e09a08 (patch)
tree5f8439d45b8ed972201dfcbdc8dd88533e88cd97 /MAINTAINERS
parentmac80211: fix mesh forwarding (diff)
downloadkernel-qcow2-linux-554d1d027b19265c4aa3f718b3126d2b86e09a08.tar.gz
kernel-qcow2-linux-554d1d027b19265c4aa3f718b3126d2b86e09a08.tar.xz
kernel-qcow2-linux-554d1d027b19265c4aa3f718b3126d2b86e09a08.zip
iwlagn: enable only rfkill interrupt when device is down
Since commit 6cd0b1cb872b3bf9fc5de4536404206ab74bafdd "iwlagn: fix hw-rfkill while the interface is down", we enable interrupts when device is not ready to receive them. However hardware, when it is in some inconsistent state, can generate other than rfkill interrupts and crash the system. I can reproduce crash with "kernel BUG at drivers/net/wireless/iwlwifi/iwl-agn.c:1010!" message, when forcing firmware restarts. To fix only enable rfkill interrupt when down device and after probe. I checked patch on laptop with 5100 device, rfkill change is still passed to user space when device is down. Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com> Cc: stable@kernel.org Acked-by: Wey-Yi Guy <wey-yi.w.guy@intel.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'MAINTAINERS')
0 files changed, 0 insertions, 0 deletions