ath9k: Use GFP_ATOMIC when allocating TX private area
authorLuis R. Rodriguez <lrodriguez@atheros.com>
Wed, 3 Dec 2008 11:35:30 +0000 (03:35 -0800)
committerJohn W. Linville <linville@tuxdriver.com>
Fri, 5 Dec 2008 14:35:59 +0000 (09:35 -0500)
commitc112d0c5b89037dd618083b5fdf4bb36b0c51d77
tree195a14b4482ef3506ffa51caa4ab7f6a5b58e003
parentf8316df10c4e3bec5b4c3a5a8e026c577640c3a6
ath9k: Use GFP_ATOMIC when allocating TX private area

Using GFP_KERNEL was wrong and produces a 'scheduling while atomic'
bug as we're in a tasklet. Also, check for proper return values
now, in case allocation fails and be sure to stop the TX queue
in case of memory issues but gaurantee the TX queue will
eventually be woken up.

Signed-off-by: Senthil Balasubramanian <senthilkumar@atheros.com>
Signed-off-by: Sujith <Sujith.Manoharan@atheros.com>
Signed-off-by: Luis R. Rodriguez <lrodriguez@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
drivers/net/wireless/ath9k/xmit.c