Bruce Allan 12d43f7d3c e1000e: unexpected "Reset adapter" message when cable pulled ... When there is heavy traffic and the cable is pulled, the driver must reset the adapter to flush the Tx queue in hardware. This causes the reset path to be scheduled and logs the message "Reset adapter" which could be mis- interpreted as an error by the user. Change how the reset path is invoked for this scenario by using the same method done in an existing work-around for 80003es2lan (i.e. set a flag and if the flag is set in the reset code do not log the "Reset adapter" message since the reset is expected). Re-name the FLAG_RX_RESTART_NOW to FLAG_RESTART_NOW since it is used for resets in both the Rx and Tx specific code. Signed-off-by: Bruce Allan <bruce.w.allan@intel.com> Tested-by: Aaron Brown <aaron.f.brown@intel.com> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>		2013-01-15 23:32:23 -08:00
..
e1000	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
e1000e	e1000e: unexpected "Reset adapter" message when cable pulled	2013-01-15 23:32:23 -08:00
igb	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
igbvf	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
ixgb	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
ixgbe	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
ixgbevf	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
e100.c	remove init of dev->perm_addr in drivers	2013-01-08 18:00:48 -08:00
Kconfig	drivers/net: remove orphaned references to micro channel	2013-01-06 21:13:33 -08:00
Makefile