summaryrefslogtreecommitdiffstats
path: root/drivers/s390/net/qeth_core.h
diff options
context:
space:
mode:
authorJulian Wiedmann2019-04-17 18:17:30 +0200
committerDavid S. Miller2019-04-17 19:33:59 +0200
commitfdd1a5303efb03bfa4016f29a519f0e553739069 (patch)
tree5dda3a632f0409c468e14e6edd4949b70964dfa6 /drivers/s390/net/qeth_core.h
parents390/qeth: handle error from qeth_update_from_chp_desc() (diff)
downloadkernel-qcow2-linux-fdd1a5303efb03bfa4016f29a519f0e553739069.tar.gz
kernel-qcow2-linux-fdd1a5303efb03bfa4016f29a519f0e553739069.tar.xz
kernel-qcow2-linux-fdd1a5303efb03bfa4016f29a519f0e553739069.zip
s390/qeth: don't bother updating the last-tx time
As the documentation for netif_trans_update() says, netdev_start_xmit() already updates the last-tx time after every good xmit. So don't duplicate that effort. One odd case is that qeth_flush_buffers() also gets called from our TX completion handler, to flush out any partially filled buffer when we switch the queue to non-packing mode. But as the TX completion handler will _always_ wake the txq, we don't have to worry about the TX watchdog there. Signed-off-by: Julian Wiedmann <jwi@linux.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/s390/net/qeth_core.h')
0 files changed, 0 insertions, 0 deletions