From: "Chuck Lever" <cel@kernel.org>
To: "Chenguang Zhao" <zhaochenguang@kylinos.cn>,
"Trond Myklebust" <trondmy@kernel.org>,
"Anna Schumaker" <anna@kernel.org>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Jeff Layton" <jlayton@kernel.org>, NeilBrown <neil@brown.name>,
"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>
Cc: linux-nfs@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND linux-next] SUNRPC: Optimize list definition method
Date: Fri, 05 Dec 2025 12:41:21 -0500 [thread overview]
Message-ID: <dd196d82-6c38-4aa3-bdb5-228fe66f4e5b@app.fastmail.com> (raw)
In-Reply-To: <20251204011232.41487-1-zhaochenguang@kylinos.cn>
On Wed, Dec 3, 2025, at 8:12 PM, Chenguang Zhao wrote:
> Integrate list definition and initialization into LIST_HEAD macro
>
> Signed-off-by: Chenguang Zhao <zhaochenguang@kylinos.cn>
> ---
> net/sunrpc/backchannel_rqst.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/net/sunrpc/backchannel_rqst.c b/net/sunrpc/backchannel_rqst.c
> index caa94cf57123..949022c5574c 100644
> --- a/net/sunrpc/backchannel_rqst.c
> +++ b/net/sunrpc/backchannel_rqst.c
> @@ -131,7 +131,7 @@ EXPORT_SYMBOL_GPL(xprt_setup_backchannel);
> int xprt_setup_bc(struct rpc_xprt *xprt, unsigned int min_reqs)
> {
> struct rpc_rqst *req;
> - struct list_head tmp_list;
> + LIST_HEAD(tmp_list);
> int i;
>
> dprintk("RPC: setup backchannel transport\n");
> @@ -147,7 +147,6 @@ int xprt_setup_bc(struct rpc_xprt *xprt, unsigned
> int min_reqs)
> * lock is held on the rpc_xprt struct. It also makes cleanup
> * easier in case of memory allocation errors.
> */
> - INIT_LIST_HEAD(&tmp_list);
> for (i = 0; i < min_reqs; i++) {
> /* Pre-allocate one backchannel rpc_rqst */
> req = xprt_alloc_bc_req(xprt);
> --
> 2.25.1
The commit message:
> SUNRPC: Optimize list definition method
>
> Integrate list definition and initialization into LIST_HEAD macro
Only describes what the change does, not why it's needed. The body
just restates the diff in English.
A commit message should justify the change. For this patch, there's
no justification. Moreover the word "Optimize" in the subject is
misleading - it implies a benefit that doesn't exist.
If this change were genuinely needed, the commit message should
explain something like:
- "...to match the pattern used elsewhere in this file" (if applicable)
- "...as a prerequisite for X"
- "...to fix Y"
For example, is this patch part of a kernel-wide audit driven by a
code safety concern?
--
Chuck Lever
prev parent reply other threads:[~2025-12-05 17:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 1:12 Chenguang Zhao
2025-12-05 17:41 ` Chuck Lever [this message]
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=dd196d82-6c38-4aa3-bdb5-228fe66f4e5b@app.fastmail.com \
--to=cel@kernel.org \
--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=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neil@brown.name \
--cc=netdev@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=pabeni@redhat.com \
--cc=tom@talpey.com \
--cc=trondmy@kernel.org \
--cc=zhaochenguang@kylinos.cn \
/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®