summaryrefslogtreecommitdiffstats
path: root/drivers/net/skge.c
diff options
context:
space:
mode:
authorInaky Perez-Gonzalez <inaky@linux.intel.com>2009-05-08 08:58:51 -0700
committerInaky Perez-Gonzalez <inaky@linux.intel.com>2009-06-11 03:30:18 -0700
commitfff1068559a2ae00a036b80c5df3c564fc6c6305 (patch)
treebe56841153c1bb258e7d535a9c84a851336c4ffa /drivers/net/skge.c
parentfb10167478a3a8e29fe122a7bf4c67b5cfc48a1b (diff)
downloadkernel-crypto-fff1068559a2ae00a036b80c5df3c564fc6c6305.tar.gz
kernel-crypto-fff1068559a2ae00a036b80c5df3c564fc6c6305.tar.xz
kernel-crypto-fff1068559a2ae00a036b80c5df3c564fc6c6305.zip
wimax/i2400m: don't call netif_start_queue() in _tx_msg_sent()
Reported and fixed by Cindy H Kao. When the device is stopped __i2400m_dev_stop() stops the network queue. However, when this is done in the middle of heavy network operation, when the bus-specific subdriver is still wrapping up and it reports a sent TX transaction with _tx_msg_sent() right after the device was stopped, the queue was being started again, which was causing a stream of oopsen and finally a panic. In any case, said call has no place there. It's a left over from an early implementation that was discarded later on. Signed-off-by: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Diffstat (limited to 'drivers/net/skge.c')
0 files changed, 0 insertions, 0 deletions