From: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>,
arnd@arndb.de, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, nathan@kernel.org, nsc@kernel.org,
ojeda@kernel.org, masahiroy@kernel.org, linux@weissschuh.net,
tamird@kernel.org, rostedt@goodmis.org, ihor.solodrai@linux.dev,
ritesh.list@gmail.com, maddy@linux.ibm.com, peterz@infradead.org
Subject: Re: [PATCH v2] char: nvram: Remove unused nvram_mutex to fix -Wunused-variable warning
Date: Mon, 23 Mar 2026 11:14:31 +0100 [thread overview]
Message-ID: <e6db8617-6b12-4f90-967d-85c9f7805823@kernel.org> (raw)
In-Reply-To: <20260323073220.25798-1-venkat88@linux.ibm.com>
Le 23/03/2026 à 08:32, Venkat Rao Bagalkote a écrit :
> v2:
> - Added missing Suggested-by tag from Ritesh Harjani (IBM)
>
Patch history must go _after_ the --- below, otherwise it will appear in
the commit message when applied, which is pointless.
> drivers/char/nvram.c defines a static mutex 'nvram_mutex' which is never
> used. This results in a compiler warning on linux-next builds:
It is probably not only linux-next builds, I think the problem exists
since 20e07af71f34 ("powerpc: Adopt nvram module for PPC64")
>
> warning: 'nvram_mutex' defined but not used [-Wunused-variable]
>
> Remove the unused definition to avoid the warning.
It is not what you are doing.
You are just hiding the probleme by saying 'maybe it is used, maybe it
is not used, I don't know I don't care". Please properly fix the problem
instead.
I think the fix is probably to remove the #ifdef CONFIG_PPC32 around
IOC_NVRAM_SYNC.
If you think it is important to return -ENOTTY on CONFIG_PPC64, just add:
diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c
index 9eff426a9286..2fd744bf9093 100644
--- a/drivers/char/nvram.c
+++ b/drivers/char/nvram.c
@@ -308,8 +308,10 @@ static long nvram_misc_ioctl(struct file *file,
unsigned int cmd,
}
#endif
break;
-#ifdef CONFIG_PPC32
case IOC_NVRAM_SYNC:
+ if (IS_ENABLED(CONFIG_PPC64))
+ break;
+
if (ppc_md.nvram_sync != NULL) {
mutex_lock(&nvram_mutex);
ppc_md.nvram_sync();
@@ -317,7 +319,6 @@ static long nvram_misc_ioctl(struct file *file,
unsigned int cmd,
}
ret = 0;
break;
-#endif
#elif defined(CONFIG_X86) || defined(CONFIG_M68K)
case NVRAM_INIT:
/* initialize NVRAM contents and checksum */
>
> Suggested-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
> Signed-off-by: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
> ---
> drivers/char/nvram.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/char/nvram.c b/drivers/char/nvram.c
> index 9eff426a9286..2ce3307663ed 100644
> --- a/drivers/char/nvram.c
> +++ b/drivers/char/nvram.c
> @@ -53,7 +53,7 @@
> #include <asm/nvram.h>
> #endif
>
> -static DEFINE_MUTEX(nvram_mutex);
> +static __maybe_unused DEFINE_MUTEX(nvram_mutex);
> static DEFINE_SPINLOCK(nvram_state_lock);
> static int nvram_open_cnt; /* #times opened */
> static int nvram_open_mode; /* special open modes */
next prev parent reply other threads:[~2026-03-23 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 7:32 [PATCH v2] char: nvram: Remove unused nvram_mutex to fix -Wunused-variable warning Venkat Rao Bagalkote
2026-03-23 7:50 ` Greg KH
2026-03-23 10:14 ` Christophe Leroy (CS GROUP) [this message]
2026-03-23 17:58 ` Arnd Bergmann
2026-03-25 9:04 ` Ritesh Harjani
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=e6db8617-6b12-4f90-967d-85c9f7805823@kernel.org \
--to=chleroy@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=ihor.solodrai@linux.dev \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@kernel.org \
--cc=ojeda@kernel.org \
--cc=peterz@infradead.org \
--cc=ritesh.list@gmail.com \
--cc=rostedt@goodmis.org \
--cc=tamird@kernel.org \
--cc=venkat88@linux.ibm.com \
/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