From: "Chuck Lever" <cel@kernel.org>
To: "Sean Chang" <seanwascoding@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Chuck Lever" <chuck.lever@oracle.com>,
"David Laight" <david.laight.linux@gmail.com>,
"Anna Schumaker" <anna@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
netdev@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sunrpc: simplify dprintk() macros and cleanup redundant debug guards
Date: Thu, 12 Mar 2026 13:52:58 -0400 [thread overview]
Message-ID: <63721454-ffbe-4725-b2c3-843560a3d5e0@app.fastmail.com> (raw)
In-Reply-To: <CAAb=EJViPvhD_ndONoU=OPcD_EXpA0Mh8500NJ9g9W_X0SpYRA@mail.gmail.com>
On Thu, Mar 12, 2026, at 11:54 AM, Sean Chang wrote:
> On Thu, Mar 12, 2026 at 9:20 PM Chuck Lever <cel@kernel.org> wrote:
>>
>> Has a subsystem tree been chosen through which to merge these two patches?
>>
>
> Hi Chuck,
> To make the review and merging process easier across different
> subsystems, I will
> send v3 as a 3-patch series:
> [PATCH v3 1/3] sunrpc: Fix dprintk type mismatch using do-while(0)
> include/linux/sunrpc/debug.h
> [PATCH v3 2/3] nfsd/lockd: Remove redundant debug checks
> fs/nfsd/nfsfh.c, fs/lockd/svclock.c
> [PATCH v3 3/3] sunrpc/xprtrdma: Simplify variable declarations and debug checks
> net/sunrpc/xprtrdma/svc_rdma_transport.c
I can take all three of those, if that's what you'd like. Just let
me know when the review is complete.
--
Chuck Lever
next prev parent reply other threads:[~2026-03-12 17:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 14:07 Sean Chang
2026-03-11 21:47 ` Andy Shevchenko
2026-03-12 13:19 ` Chuck Lever
2026-03-12 15:54 ` Sean Chang
2026-03-12 16:14 ` Andy Shevchenko
2026-03-12 17:52 ` Chuck Lever [this message]
2026-03-17 13:04 ` Sean Chang
2026-03-17 14:20 ` Andy Shevchenko
2026-03-18 16:21 ` Sean Chang
2026-03-18 16:40 ` 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=63721454-ffbe-4725-b2c3-843560a3d5e0@app.fastmail.com \
--to=cel@kernel.org \
--cc=andrew@lunn.ch \
--cc=andriy.shevchenko@intel.com \
--cc=anna@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=david.laight.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=seanwascoding@gmail.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
all inboxes | Powered by JetHome®