summaryrefslogtreecommitdiffstats
path: root/net/decnet
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2021-08-03 12:58:22 +0100
committerDavid S. Miller <davem@davemloft.net>2021-08-03 12:58:22 +0100
commit2dbf4c2e7e3da6158305e618b340419ea12a6909 (patch)
tree55e8a56bf50929280aa1eb05ef8229c05970fc11 /net/decnet
parentc32325b8fdf2f979befb9fd5587918c0d5412db3 (diff)
parentd43c65b05b848e0b2db1a6c78b02c189da3a95b5 (diff)
downloadlinux-2dbf4c2e7e3da6158305e618b340419ea12a6909.tar.bz2
Merge branch 'ethtool-runtime-pm'
Heiner Kallweit says: ==================== ethtool: runtime-resume netdev parent before ethtool ops If a network device is runtime-suspended then: - network device may be flagged as detached and all ethtool ops (even if not accessing the device) will fail because netif_device_present() returns false - ethtool ops may fail because device is not accessible (e.g. because being in D3 in case of a PCI device) It may not be desirable that userspace can't use even simple ethtool ops that not access the device if interface or link is down. To be more friendly to userspace let's ensure that device is runtime-resumed when executing ethtool ops in kernel. This patch series covers the typical case that the netdev parent is power- managed, e.g. a PCI device. Not sure whether cases exist where the netdev itself is power-managed. If yes then we may need an extension for this. But the series as-is at least shouldn't cause problems in that case. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/decnet')
0 files changed, 0 insertions, 0 deletions