public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Mina Almasry <almasrymina@google.com>
To: linux-kernel@vger.kernel.org
Cc: Mina Almasry <almasrymina@google.com>,
	kuba@kernel.org, asml.silence@gmail.com,  sdf@fomichev.me,
	byungchul@sk.com, io-uring@vger.kernel.org,
	 netdev@vger.kernel.org
Subject: [PATCH RFC net-next v1] net: Add maintainer entry for netmem & friends
Date: Thu, 21 Aug 2025 02:56:16 +0000	[thread overview]
Message-ID: <20250821025620.552728-1-almasrymina@google.com> (raw)

There is some needless friction with regards to whether netmem_ref,
net_iov, and memory provider patches being CC'd to netdev or not. Add
clear policy and put it in the MAINTAINERS file so get_maintainer.pl
does the right thing by default.

All changes to current and future memory providers should be CC'd to
netdev. The devmem memory provider happens to be under net so is
covered by 'NETWORKING [GENERAL]' as-is. The io_uring memory provider
happens to be outside of net/ though, so add an explicit file entry
for that.

Note that the memory provider changes need _not_ be merged through net
or net-next, but the changes should be CC'd to netdev. Target the
appropriate tree using the [PATCH ...] prefix.

All changes using or modifying netmem_ref or struct net_iov should also
be sent to netdev, so add a content regex for that. Patches modifying
the netmem_ref or net_iov infra should also target net or net-next
([PATCH net] or [PATCH net-next]). This is already the convention.

Note that no maintainers or reviewers are dedicated to this entry.
We don't presume to overburden existing maintainers or add new ones; let
the maintainers nominate folks whenever they feel appropriate. But make
sure changes are sent to the correct lists.

Tested by creating a couple of trivial changes in io_uring/zcrx.[h|c]
and adding netmem_ref and net_iov in other subsystems, and looking at
the get_maintainer.pl results.

Signed-off-by: Mina Almasry <almasrymina@google.com>

---

Cc: kuba@kernel.org
Cc: asml.silence@gmail.com
Cc: sdf@fomichev.me
Cc: byungchul@sk.com
Cc: io-uring@vger.kernel.org
Cc: netdev@vger.kernel.org
---
 MAINTAINERS | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 4dcce7a5894b..22c50aeefaa5 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17853,6 +17853,17 @@ F:	include/uapi/linux/unix_diag.h
 F:	net/unix/
 F:	tools/testing/selftests/net/af_unix/
 
+NETWORKING [NETMEM, NET_IOV & MEMORY PROVIDERS]
+L:	netdev@vger.kernel.org
+S:	Maintained
+Q:	https://patchwork.kernel.org/project/netdevbpf/list/
+B:	mailto:netdev@vger.kernel.org
+P:	Documentation/process/maintainer-netdev.rst
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git
+T:	git git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git
+F:	io_uring/zcrx.*
+K:	\bnet(mem_ref|_iov)\b
+
 NETXEN (1/10) GbE SUPPORT
 M:	Manish Chopra <manishc@marvell.com>
 M:	Rahul Verma <rahulv@marvell.com>

base-commit: 62a2b3502573091dc5de3f9acd9e47f4b5aac9a1
-- 
2.51.0.rc1.193.gad69d77794-goog


                 reply	other threads:[~2025-08-21  2:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20250821025620.552728-1-almasrymina@google.com \
    --to=almasrymina@google.com \
    --cc=asml.silence@gmail.com \
    --cc=byungchul@sk.com \
    --cc=io-uring@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sdf@fomichev.me \
    /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