Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Gerd Bayer <gbayer@linux.ibm.com>
To: 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>,
	Leon Romanovsky <leon@kernel.org>
Cc: 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, Gerd Bayer <gbayer@linux.ibm.com>
Subject: [PATCH net-next] net/smc: Run patches also by RDMA ML
Date: Fri, 15 Nov 2024 18:44:57 +0100	[thread overview]
Message-ID: <20241115-smc_lists-v1-1-a0a438125f13@linux.ibm.com> (raw)

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
 S:	Supported
 F:	net/smc/

---
base-commit: 519b790af22e705ee3fae7d598f1afbb3d1cfdd5
change-id: 20241106-smc_lists-b98e6829b31c

Best regards,
-- 
Gerd Bayer <gbayer@linux.ibm.com>


             reply	other threads:[~2024-11-15 17:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-15 17:44 Gerd Bayer [this message]
2024-11-17 10:01 ` [PATCH net-next] net/smc: Run patches also by RDMA ML Leon Romanovsky
2024-11-18  8:46   ` Gerd Bayer
2024-11-18  9:37     ` Leon Romanovsky
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=20241115-smc_lists-v1-1-a0a438125f13@linux.ibm.com \
    --to=gbayer@linux.ibm.com \
    --cc=alibuda@linux.alibaba.com \
    --cc=guwen@linux.alibaba.com \
    --cc=jaka@linux.ibm.com \
    --cc=leon@kernel.org \
    --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