diff options
author | Jakub Kicinski <kuba@kernel.org> | 2024-04-06 08:11:28 +0300 |
---|---|---|
committer | Jakub Kicinski <kuba@kernel.org> | 2024-04-06 08:11:29 +0300 |
commit | 4196aee00e2ecc274dd46ee4b20d85ec9145ca70 (patch) | |
tree | b5b3cd6b813247c2d55b8e7042217caa1eb2bbb5 /Documentation/networking | |
parent | 386f4a737964702e4364376285afd61315ae3c28 (diff) | |
parent | 0ef416e045ad7083933b469b6ca7968d1cc0eb80 (diff) | |
download | linux-4196aee00e2ecc274dd46ee4b20d85ec9145ca70.tar.xz |
Merge branch 'address-all-wunused-const-warnings'
Arnd Bergmann says:
====================
address all -Wunused-const warnings (the net part)
Compilers traditionally warn for unused 'static' variables, but not
if they are constant. The reason here is a custom for C++ programmers
to define named constants as 'static const' variables in header files
instead of using macros or enums.
In W=1 builds, we get warnings only static const variables in C
files, but not in headers, which is a good compromise, but this still
produces warning output in at least 30 files. These warnings are
almost all harmless, but also trivial to fix, and there is no
good reason to warn only about the non-const variables being unused.
I've gone through all the files that I found using randconfig and
allmodconfig builds and created patches to avoid these warnings,
with the goal of retaining a clean build once the option is enabled
by default.
Unfortunately, there is one fairly large patch ("drivers: remove
incorrect of_match_ptr/ACPI_PTR annotations") that touches
34 individual drivers that all need the same one-line change.
If necessary, I can split it up by driver or by subsystem,
but at least for reviewing I would keep it as one piece for
the moment.
====================
Link: https://lore.kernel.org/r/20240403080702.3509288-1-arnd@kernel.org
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'Documentation/networking')
0 files changed, 0 insertions, 0 deletions