From: Jakub Kicinski <kuba@kernel•org>
To: "kexinsun@smail•nju.edu.cn" <kexinsun@smail•nju.edu.cn>
Cc: Allison Henderson <allison.henderson@oracle•com>,
"linux-rdma@vger•kernel.org" <linux-rdma@vger•kernel.org>,
"yunbolyu@smu•edu.sg" <yunbolyu@smu•edu.sg>,
"davem@davemloft•net" <davem@davemloft•net>,
"ratnadiraw@smu•edu.sg" <ratnadiraw@smu•edu.sg>,
"rds-devel@oss•oracle.com" <rds-devel@oss•oracle.com>,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
"julia.lawall@inria•fr" <julia.lawall@inria•fr>,
"pabeni@redhat•com" <pabeni@redhat•com>,
"horms@kernel•org" <horms@kernel•org>,
"edumazet@google•com" <edumazet@google•com>,
"xutong.ma@inria•fr" <xutong.ma@inria•fr>,
"netdev@vger•kernel.org" <netdev@vger•kernel.org>
Subject: Re: [PATCH] rds: update outdated comment
Date: Wed, 25 Feb 2026 19:05:14 -0800 [thread overview]
Message-ID: <20260225190514.01a905d7@kernel.org> (raw)
In-Reply-To: <2e555525ab0bcec255c9c73a8457ba4a9466ee6e.camel@oracle.com>
On Wed, 25 Feb 2026 03:03:10 +0000 Allison Henderson wrote:
> Thanks for the catch. Just one small nit: Your patch should specify the target
> branch, version and component like this:
>
> [PATCH net-next v2] net/rds: update outdated comment in rds_send_xmit
That's right, please try to remember the tree name in the future.
Since net-next is our default tree anyway, there's no need to repost
next prev parent reply other threads:[~2026-02-26 3:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 2:07 [PATCH] rds: update outdated comment kexinsun
2026-02-25 3:03 ` Allison Henderson
2026-02-26 3:05 ` Jakub Kicinski [this message]
2026-02-26 3:10 ` patchwork-bot+netdevbpf
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=20260225190514.01a905d7@kernel.org \
--to=kuba@kernel$(echo .)org \
--cc=allison.henderson@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=horms@kernel$(echo .)org \
--cc=julia.lawall@inria$(echo .)fr \
--cc=kexinsun@smail$(echo .)nju.edu.cn \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-rdma@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=ratnadiraw@smu$(echo .)edu.sg \
--cc=rds-devel@oss$(echo .)oracle.com \
--cc=xutong.ma@inria$(echo .)fr \
--cc=yunbolyu@smu$(echo .)edu.sg \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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