diff options
| author |   David S. Miller <davem@davemloft.net> | 2020-03-05 21:38:03 -0800 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2020-03-05 21:38:03 -0800 |
| commit | 425c075dcbb2009a526fffb40ada846acc40d2b1 (patch) | |
| tree | c00a3f377be07758e4dcccafd987a3d8022acbb1 /drivers/net/ethernet/intel/ice/ice_ethtool.c | |
| parent | tc-testing: updated tdc tests for basic filter with canid extended match rules (diff) | |
| parent | tun: drop TUN_DEBUG and tun_debug() (diff) | |
| download | wireguard-linux-425c075dcbb2009a526fffb40ada846acc40d2b1.tar.xz wireguard-linux-425c075dcbb2009a526fffb40ada846acc40d2b1.zip | |
Merge branch 'tun-debug'
Michal Kubecek says:
====================
tun: debug messages cleanup
While testing ethtool output for "strange" devices, I noticed confusing and
obviously incorrect message level information for a tun device and sent
a quick fix. The result of the upstream discussion was that tun driver
would rather deserve a more complex cleanup of the way it handles debug
messages.
The main problem is that all debugging statements and setting of message
level are controlled by TUN_DEBUG macro which is only defined if one edits
the source and rebuilds the module, otherwise all DBG1() and tun_debug()
statements do nothing.
This series drops the TUN_DEBUG switch and replaces custom tun_debug()
macro with standard netif_info() so that message level (mask) set and
displayed using ethtool works as expected. Some debugging messages are
dropped as they only notify about entering a function which can be done
easily using ftrace or kprobe.
Patch 1 is a trivial fix for compilation warning with W=1.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_ethtool.c')
0 files changed, 0 insertions, 0 deletions