From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Jeff Layton <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, llvm@lists.linux.dev,
Trond Myklebust <trondmy@kernel.org>,
Anna Schumaker <anna@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <Dai.Ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <nick.desaulniers+lkml@gmail.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>
Subject: Re: [PATCH v2 0/3] sunrpc: Fix `make W=1` build issues
Date: Wed, 4 Feb 2026 16:45:26 +0200 [thread overview]
Message-ID: <aYNbhhJJgpv0TjmY@smile.fi.intel.com> (raw)
In-Reply-To: <65f86149-eafe-4f83-ac18-f3aedd516152@oracle.com>
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
next prev parent reply other threads:[~2026-02-04 14:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 9:41 [PATCH v2 0/3] sunrpc: Fix `make W=1` build issues Andy Shevchenko
2026-02-04 9:41 ` [PATCH v2 1/3] nfs/blocklayout: Fix compilation error (`make W=1`) in bl_write_pagelist() Andy Shevchenko
2026-02-04 15:53 ` Anna Schumaker
2026-02-04 16:44 ` Andy Shevchenko
2026-02-04 9:41 ` [PATCH v2 2/3] sunrpc: Kill RPC_IFDEBUG() Andy Shevchenko
2026-02-04 9:41 ` [PATCH v2 3/3] sunrpc: Fix compilation error (`make W=1`) when dprintk() is no-op Andy Shevchenko
2026-02-04 16:46 ` Andy Shevchenko
2026-02-04 16:58 ` Andy Shevchenko
2026-02-04 18:29 ` Chuck Lever
2026-02-04 20:25 ` Andy Shevchenko
2026-02-04 10:02 ` [PATCH v2 0/3] sunrpc: Fix `make W=1` build issues Andy Shevchenko
2026-02-04 14:28 ` Jeff Layton
2026-02-04 14:30 ` Chuck Lever
2026-02-04 14:45 ` Andy Shevchenko [this message]
2026-02-04 14:32 ` Andy Shevchenko
2026-02-04 15:42 ` Chuck Lever
2026-02-04 15:51 ` 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=aYNbhhJJgpv0TjmY@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Dai.Ngo@oracle.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jlayton@kernel.org \
--cc=justinstitt@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.