diff options
| author | Peter Zijlstra <[email protected]> | 2025-11-06 10:50:00 +0000 |
|---|---|---|
| committer | Nathan Chancellor <[email protected]> | 2025-11-07 18:19:53 +0000 |
| commit | 9818af18db4bfefd320d0fef41390a616365e6f7 (patch) | |
| tree | 4432249ac7e7223ce4d7bde095502578209fca67 /net/unix/af_unix.c | |
| parent | kbuild: Strip trailing padding bytes from modules.builtin.modinfo (diff) | |
| download | kernel-9818af18db4bfefd320d0fef41390a616365e6f7.tar.gz kernel-9818af18db4bfefd320d0fef41390a616365e6f7.zip | |
compiler_types: Move unused static inline functions warning to W=2
Per Nathan, clang catches unused "static inline" functions in C files
since commit 6863f5643dd7 ("kbuild: allow Clang to find unused static
inline functions for W=1 build").
Linus said:
> So I entirely ignore W=1 issues, because I think so many of the extra
> warnings are bogus.
>
> But if this one in particular is causing more problems than most -
> some teams do seem to use W=1 as part of their test builds - it's fine
> to send me a patch that just moves bad warnings to W=2.
>
> And if anybody uses W=2 for their test builds, that's THEIR problem..
Here is the change to bump the warning from W=1 to W=2.
Fixes: 6863f5643dd7 ("kbuild: allow Clang to find unused static inline functions for W=1 build")
Signed-off-by: Peter Zijlstra <[email protected]>
Signed-off-by: Andy Shevchenko <[email protected]>
Link: https://patch.msgid.link/[email protected]
[nathan: Adjust comment as well]
Signed-off-by: Nathan Chancellor <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions
