netdev - Re: [PATCH v2 0/3] sunrpc: Fix `make W=1` build issues

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aYNbhhJJgpv0TjmY@smile.fi.intel.com>
Date: Wed, 4 Feb 2026 16:45:26 +0200
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Chuck Lever <chuck.lever@...cle.com>
Cc: Jeff Layton <jlayton@...nel.org>, NeilBrown <neil@...wn.name>,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	netdev@...r.kernel.org, llvm@...ts.linux.dev,
	Trond Myklebust <trondmy@...nel.org>,
	Anna Schumaker <anna@...nel.org>,
	Olga Kornievskaia <okorniev@...hat.com>,
	Dai Ngo <Dai.Ngo@...cle.com>, Tom Talpey <tom@...pey.com>,
	"David S. Miller" <davem@...emloft.net>,
	Eric Dumazet <edumazet@...gle.com>,
	Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
	Simon Horman <horms@...nel.org>,
	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 v2 0/3] sunrpc: Fix `make W=1` build issues

On Wed, Feb 04, 2026 at 09:30:30AM -0500, Chuck Lever wrote:
> On 2/4/26 9:28 AM, Jeff Layton wrote:
> > On Wed, 2026-02-04 at 10:41 +0100, Andy Shevchenko wrote:

...

> >> Andy Shevchenko (3):
> >>   nfs/blocklayout: Fix compilation error (`make W=1`) in
> >>     bl_write_pagelist()
> >>   sunrpc: Kill RPC_IFDEBUG()
> >>   sunrpc: Fix compilation error (`make W=1`) when dprintk() is no-op

> > These all look like good changes to me. The first patch should go to
> > Trond/Anna and Chuck will probably pick up the other two?

> That's what I was thinking, as long as there aren't any dependencies
> between 1/3 and the others.

There are no explicit compilation dependencies, but if one will wonder
in the future the third patch alone may "fix" the first issue. That's
why I prefer them going together.

-- 
With Best Regards,
Andy Shevchenko