[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aSgCyqR72Zu6TSSI@black.igk.intel.com>
Date: Thu, 27 Nov 2025 08:50:34 +0100
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Chuck Lever <cel@...nel.org>
Cc: linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
llvm@...ts.linux.dev, Chuck Lever <chuck.lever@...cle.com>,
Jeff Layton <jlayton@...nel.org>, NeilBrown <neil@...wn.name>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>, Tom Talpey <tom@...pey.com>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <nick.desaulniers+lkml@...il.com>,
Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>
Subject: Re: [PATCH v1 1/1] nfsd: Mark variable __maybe_unused to avoid W=1
build break
On Mon, Nov 17, 2025 at 08:49:29AM -0500, Chuck Lever wrote:
> On Thu, 13 Nov 2025 09:31:31 +0100, Andy Shevchenko wrote:
> > Clang is not happy about set but (in some cases) unused variable:
> >
> > fs/nfsd/export.c:1027:17: error: variable 'inode' set but not used [-Werror,-Wunused-but-set-variable]
> >
> > since it's used as a parameter to dprintk() which might be configured
> > a no-op. To avoid uglifying code with the specific ifdeffery just mark
> > the variable __maybe_unused.
[...]
> Applied to nfsd-testing, thanks!
>
> [1/1] nfsd: Mark variable __maybe_unused to avoid W=1 build break
> commit: 56e9f88b25abf08de6f2b1bfbbb2ddc4e6622d1e
Thanks, but still no appearance in Linux Next and problem seems to be present.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists