From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: <netdev@vger.kernel.org>
Subject: [PATCH net] MAINTAINERS: Add the new IPsec list and patchwork instance
Date: Mon, 9 Nov 2026 09:23:08 +0100 [thread overview]
Message-ID: <avGC7CrPVgMrBBtq@gauss4> (raw)
We now have a dedicated mailing list and patchwork instance for
IPsec. Patches for the ipsec and ipsec-next tree should be
submitted to netdev@vger.kernel.org and ipsec@lists.linux.dev,
so that the new IPsec patchwork instance can track it.
Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
---
I targeted the patch to net so that the new workflow gets
implemented faster. But if there are concerns to apply it
to net, it can also go to net-next.
MAINTAINERS | 2 ++
1 file changed, 2 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 09713dc4c6a7..36767254c33c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19506,7 +19506,9 @@ M: Steffen Klassert <steffen.klassert@secunet.com>
M: Herbert Xu <herbert@gondor.apana.org.au>
M: "David S. Miller" <davem@davemloft.net>
L: netdev@vger.kernel.org
+L: ipsec@lists.linux.dev
S: Maintained
+Q: https://patchwork.kernel.org/project/ipsec/list/
T: git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec.git
T: git git://git.kernel.org/pub/scm/linux/kernel/git/klassert/ipsec-next.git
F: Documentation/networking/xfrm/
--
2.53.0
next reply other threads:[~2026-11-09 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:23 Steffen Klassert [this message]
2026-11-11 0:00 ` [PATCH net] MAINTAINERS: Add the new IPsec list and patchwork instance 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=avGC7CrPVgMrBBtq@gauss4 \
--to=steffen.klassert@secunet.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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