public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
	Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
	Bill Wendling <morbo@google.com>,
	Justin Stitt <justinstitt@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>,
	Jonathan Cameron <jonathan.cameron@huawei.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v1 1/1] compiler_types: Warn about unused static inline functions on second
Date: Thu, 6 Nov 2025 08:16:49 -0700	[thread overview]
Message-ID: <20251106151649.GA1693433@ax162> (raw)
In-Reply-To: <20251106105000.2103276-1-andriy.shevchenko@linux.intel.com>

On Thu, Nov 06, 2025 at 11:50:00AM +0100, Andy Shevchenko wrote:
> From: Peter Zijlstra <peterz@infradead.org>
> 
> 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 <peterz@infradead.org>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>

I can take this as a fix via kbuild or Linus can apply it directly
but...

> ---
>  include/linux/compiler_types.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/compiler_types.h b/include/linux/compiler_types.h
> index 59288a2c1ad2..575a03643fa1 100644
> --- a/include/linux/compiler_types.h
> +++ b/include/linux/compiler_types.h
> @@ -253,7 +253,7 @@ struct ftrace_likely_data {
>   * for W=1 build. This will allow clang to find unused functions. Remove the
>   * __inline_maybe_unused entirely after fixing most of -Wunused-function warnings.
>   */

The comment should be updated to W=2 instead of W=1 and we should
probably drop the sentence about removing __inline_maybe_unused entirely
since people such as Peter will never want this behavior by default. I
do not mind doing it myself if I take it.

> -#ifdef KBUILD_EXTRA_WARN1
> +#ifdef KBUILD_EXTRA_WARN2
>  #define __inline_maybe_unused
>  #else
>  #define __inline_maybe_unused __maybe_unused
> -- 
> 2.50.1
> 

  reply	other threads:[~2025-11-06 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06 10:50 [PATCH v1 1/1] compiler_types: Warn about unused static inline functions on second Andy Shevchenko
2025-11-06 15:16 ` Nathan Chancellor [this message]
2025-11-06 16:01   ` Andy Shevchenko
2025-11-06 17:06     ` Nathan Chancellor
2025-11-07  7:45       ` Andy Shevchenko
2025-11-06 19:13   ` Linus Torvalds
2025-11-07 18:29 ` Nathan Chancellor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20251106151649.GA1693433@ax162 \
    --to=nathan@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=justinstitt@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox