From: Leon Romanovsky <leon@kernel.org>
To: Gerd Bayer <gbayer@linux.ibm.com>
Cc: Wenjia Zhang <wenjia@linux.ibm.com>,
Jan Karcher <jaka@linux.ibm.com>,
"D. Wythe" <alibuda@linux.alibaba.com>,
Tony Lu <tonylu@linux.alibaba.com>,
Wen Gu <guwen@linux.alibaba.com>,
Halil Pasic <pasic@linux.ibm.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
linux390-list@tuxmaker.boeblingen.de.ibm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net/smc: Run patches also by RDMA ML
Date: Mon, 18 Nov 2024 11:37:12 +0200 [thread overview]
Message-ID: <20241118093712.GA8673@unreal> (raw)
In-Reply-To: <bd8e196839281fd324721650c5974db35b7990ec.camel@linux.ibm.com>
On Mon, Nov 18, 2024 at 09:46:28AM +0100, Gerd Bayer wrote:
> On Sun, 2024-11-17 at 12:01 +0200, Leon Romanovsky wrote:
> > On Fri, Nov 15, 2024 at 06:44:57PM +0100, Gerd Bayer wrote:
> > > Commits for the SMC protocol usually get carried through the netdev
> > > mailing list. Some portions use InfiniBand verbs that are discussed on
> > > the RDMA mailing list. So run patches by that list too to increase the
> > > likelihood that all interested parties can see them.
> > >
> > > Signed-off-by: Gerd Bayer <gbayer@linux.ibm.com>
> > > ---
> > > ---
> > > MAINTAINERS | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 32d157621b44fb919307e865e2481ab564eb17df..16024268b5fc1feb6c0d01eab3048bd9255d0bf9 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -20943,6 +20943,7 @@ M: Jan Karcher <jaka@linux.ibm.com>
> > > R: D. Wythe <alibuda@linux.alibaba.com>
> > > R: Tony Lu <tonylu@linux.alibaba.com>
> > > R: Wen Gu <guwen@linux.alibaba.com>
> > > +L: linux-rdma@vger.kernel.org
> > > L: linux-s390@vger.kernel.org
> >
>
> Hi Leon,
>
> > Why don't we have netdev ML here too?
>
> since all smc code resides in net/smc the filter tag F: net/ in
> "NETWORKING [GENERAL]" provides that. My first internal draft contained
> an explicit L: tag for the netdev ML, but I dropped it to avoid any
> redundancy.
Thanks for the explanation,
Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
next prev parent reply other threads:[~2024-11-18 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 17:44 [PATCH net-next] net/smc: Run patches also by RDMA ML Gerd Bayer
2024-11-17 10:01 ` Leon Romanovsky
2024-11-18 8:46 ` Gerd Bayer
2024-11-18 9:37 ` Leon Romanovsky [this message]
2024-11-19 4:00 ` 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=20241118093712.GA8673@unreal \
--to=leon@kernel.org \
--cc=alibuda@linux.alibaba.com \
--cc=gbayer@linux.ibm.com \
--cc=guwen@linux.alibaba.com \
--cc=jaka@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux390-list@tuxmaker.boeblingen.de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=tonylu@linux.alibaba.com \
--cc=wenjia@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).