linux/drivers/net/tulip
Erik Mouw 06f7525be4 xircom_cb should return NETDEV_TX_BUSY when no descriptors available
Changes in other networking paths uncovered a bug in the xircom_cb
driver which made the kernel spew lots of the following error messages:

  BUG eth1 code -5 qlen 0

It turned out that the driver returned -EIO when there was no
descriptor available for sending packets. It should return
NETDEV_TX_BUSY instead. This was discussed on the netdev list before,
see http://thread.gmane.org/gmane.linux.network/84603 .

Signed-off-by: Erik Mouw <mouw@nl.linux.org>
Signed-off-by: Jeff Garzik <jeff@garzik.org>
2008-02-05 13:31:29 -05:00
..
21142.c
de4x5.c [netdrvr] checkpatch cleanups 2008-01-28 15:04:05 -08:00
de4x5.h
de2104x.c
dmfe.c [TULIP] DMFE: Fix SROM parsing regression. 2008-01-23 03:11:39 -08:00
eeprom.c
interrupt.c
Kconfig
Makefile
media.c
pnic2.c
pnic.c
timer.c
tulip_core.c endianness noise in tulip_core 2008-01-12 17:33:04 -05:00
tulip.h
uli526x.c
winbond-840.c
xircom_cb.c xircom_cb should return NETDEV_TX_BUSY when no descriptors available 2008-02-05 13:31:29 -05:00
xircom_tulip_cb.c