summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorSimon Horman <horms@kernel.org>2025-03-18 16:53:34 +0300
committerJakub Kicinski <kuba@kernel.org>2025-03-25 14:32:39 +0300
commit6165feda3d8cd42663e50aa090e341e673990950 (patch)
tree9554f866fc22c05bec4a0af620f2f98e74d05fcd /tools/perf/scripts/python/stackcollapse.py
parent5555b34c581d943e3c837cc4fd75cc3b563f4726 (diff)
downloadlinux-6165feda3d8cd42663e50aa090e341e673990950.tar.xz
net: tulip: avoid unused variable warning
There is an effort to achieve W=1 kernel builds without warnings. As part of that effort Helge Deller highlighted the following warnings in the tulip driver when compiling with W=1 and CONFIG_TULIP_MWI=n: .../tulip_core.c: In function ‘tulip_init_one’: .../tulip_core.c:1309:22: warning: variable ‘force_csr0’ set but not used This patch addresses that problem using IS_ENABLED(). This approach has the added benefit of reducing conditionally compiled code. And thus increasing compile coverage. E.g. for allmodconfig builds which enable CONFIG_TULIP_MWI. Compile tested only. No run-time effect intended. Acked-by: Helge Deller <deller@gmx.de> Signed-off-by: Simon Horman <horms@kernel.org> Link: https://patch.msgid.link/20250318-tulip-w1-v3-1-a813fadd164d@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions