mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
	Boqun Feng <boqun.feng@gmail.com>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH v1 1/1] sched/fair: Mark some static const with __maybe_unused
Date: Fri, 4 Apr 2025 13:08:45 -0400	[thread overview]
Message-ID: <eba3c40a-b777-4f52-b9ce-6cae59b5f586@redhat.com> (raw)
In-Reply-To: <20250404165204.3657093-1-andriy.shevchenko@linux.intel.com>

On 4/4/25 12:52 PM, Andy Shevchenko wrote:
> GCC considers that some static const defined in the lockdep_internals.h
> are unused, which prevents `make W=1` and CONFIG_WERROR=y builds:
>
> kernel/locking/lockdep_internals.h:69:28: error: ‘LOCKF_USED_IN_IRQ_READ’ defined but not used [-Werror=unused-const-variable=]
>     69 | static const unsigned long LOCKF_USED_IN_IRQ_READ =
>        |                            ^~~~~~~~~~~~~~~~~~~~~~
> kernel/locking/lockdep_internals.h:63:28: error: ‘LOCKF_ENABLED_IRQ_READ’ defined but not used [-Werror=unused-const-variable=]
>     63 | static const unsigned long LOCKF_ENABLED_IRQ_READ =
>        |                            ^~~~~~~~~~~~~~~~~~~~~~
> kernel/locking/lockdep_internals.h:57:28: error: ‘LOCKF_USED_IN_IRQ’ defined but not used [-Werror=unused-const-variable=]
>     57 | static const unsigned long LOCKF_USED_IN_IRQ =
>        |                            ^~~~~~~~~~~~~~~~~
> kernel/locking/lockdep_internals.h:51:28: error: ‘LOCKF_ENABLED_IRQ’ defined but not used [-Werror=unused-const-variable=]
>     51 | static const unsigned long LOCKF_ENABLED_IRQ =
>        |                            ^~~~~~~~~~~~~~~~~
>
> Fix this by marking them with __maybe_unused.

The code changes look good, but the "sched/fair" heading is misleading. 
It is not related to scheduler at all, it should be "locking/lockdep" or 
just "lockdep".

Cheers,
Longman

>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
>   kernel/locking/lockdep_internals.h | 8 ++++----
>   1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/kernel/locking/lockdep_internals.h b/kernel/locking/lockdep_internals.h
> index 20f9ef58d3d0..82e71335f367 100644
> --- a/kernel/locking/lockdep_internals.h
> +++ b/kernel/locking/lockdep_internals.h
> @@ -48,25 +48,25 @@ enum {
>   };
>   
>   #define LOCKDEP_STATE(__STATE)	LOCKF_ENABLED_##__STATE |
> -static const unsigned long LOCKF_ENABLED_IRQ =
> +static __maybe_unused const unsigned long LOCKF_ENABLED_IRQ =
>   #include "lockdep_states.h"
>   	0;
>   #undef LOCKDEP_STATE
>   
>   #define LOCKDEP_STATE(__STATE)	LOCKF_USED_IN_##__STATE |
> -static const unsigned long LOCKF_USED_IN_IRQ =
> +static __maybe_unused const unsigned long LOCKF_USED_IN_IRQ =
>   #include "lockdep_states.h"
>   	0;
>   #undef LOCKDEP_STATE
>   
>   #define LOCKDEP_STATE(__STATE)	LOCKF_ENABLED_##__STATE##_READ |
> -static const unsigned long LOCKF_ENABLED_IRQ_READ =
> +static __maybe_unused const unsigned long LOCKF_ENABLED_IRQ_READ =
>   #include "lockdep_states.h"
>   	0;
>   #undef LOCKDEP_STATE
>   
>   #define LOCKDEP_STATE(__STATE)	LOCKF_USED_IN_##__STATE##_READ |
> -static const unsigned long LOCKF_USED_IN_IRQ_READ =
> +static __maybe_unused const unsigned long LOCKF_USED_IN_IRQ_READ =
>   #include "lockdep_states.h"
>   	0;
>   #undef LOCKDEP_STATE


  reply	other threads:[~2025-04-04 17:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 16:52 Andy Shevchenko
2025-04-04 17:08 ` Waiman Long [this message]
2025-04-05  9:16 ` Arnd Bergmann
2025-04-06 12:38   ` Andy Shevchenko

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=eba3c40a-b777-4f52-b9ce-6cae59b5f586@redhat.com \
    --to=llong@redhat.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=arnd@arndb.de \
    --cc=boqun.feng@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=will@kernel.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

all inboxes | Powered by JetHome®