From: Martin KaFai Lau <martin.lau@linux.dev>
To: bpf@vger.kernel.org
Cc: 'Alexei Starovoitov ' <ast@kernel.org>,
'Andrii Nakryiko ' <andrii@kernel.org>,
'Daniel Borkmann ' <daniel@iogearbox.net>,
Eduard Zingerman <eddyz87@gmail.com>,
Kumar Kartikeya Dwivedi <memxor@gmail.com>,
netdev@vger.kernel.org
Subject: [PATCH bpf-next] bpf: MAINTAINERS: Update bpf maintainers
Date: Fri, 29 May 2026 13:39:09 -0700 [thread overview]
Message-ID: <20260529203909.1222164-1-martin.lau@linux.dev> (raw)
From: Martin KaFai Lau <martin.lau@kernel.org>
I am making a life change and will take a long break
from my current work, so I will step down from the "M:" responsibility.
I am currently a "R:" in "BPF [GENERAL]", this part stays unchanged.
I am folding most of the parts into "BPF [GENERAL]".
For "BPF [BTF]", it is long overdue as I am no longer involved.
It is folded into the "BPF [GENERAL]".
The "BPF [STORAGE & CGROUPS]" will also be covered by "BPF [GENERAL]".
For struct_ops, its usage is no longer limited to networking,
so this naturally should move back to "BPF [GENERAL]".
For the reuseport, it will continue to be maintained together
by "BPF [GENERAL]" and the "NETWORKING [SOCKETS]".
For other "BPF [NETWORKING]...", I am moving myself to "R:".
Thanks!
Signed-off-by: Martin KaFai Lau <martin.lau@kernel.org>
---
MAINTAINERS | 24 +-----------------------
1 file changed, 1 insertion(+), 23 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index dfc621ff629d..d9caa2d980f1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4766,13 +4766,6 @@ S: Supported
F: arch/x86/net/
X: arch/x86/net/bpf_jit_comp32.c
-BPF [BTF]
-M: Martin KaFai Lau <martin.lau@linux.dev>
-L: bpf@vger.kernel.org
-S: Maintained
-F: include/linux/btf*
-F: kernel/bpf/btf.c
-
BPF [CORE]
M: Alexei Starovoitov <ast@kernel.org>
M: Daniel Borkmann <daniel@iogearbox.net>
@@ -4905,18 +4898,11 @@ F: tools/testing/selftests/bpf/prog_tests/tc_netkit.c
F: tools/testing/selftests/drivers/net/hw/nk_qlease.py
F: tools/testing/selftests/net/nk_qlease.py
-BPF [NETWORKING] (struct_ops, reuseport)
-M: Martin KaFai Lau <martin.lau@linux.dev>
-L: bpf@vger.kernel.org
-L: netdev@vger.kernel.org
-S: Maintained
-F: kernel/bpf/bpf_struct*
-
BPF [NETWORKING] (tcx & tc BPF, sock_addr)
-M: Martin KaFai Lau <martin.lau@linux.dev>
M: Daniel Borkmann <daniel@iogearbox.net>
R: John Fastabend <john.fastabend@gmail.com>
R: Stanislav Fomichev <sdf@fomichev.me>
+R: Martin KaFai Lau <martin.lau@linux.dev>
L: bpf@vger.kernel.org
L: netdev@vger.kernel.org
S: Maintained
@@ -4951,14 +4937,6 @@ L: bpf@vger.kernel.org
S: Maintained
F: tools/testing/selftests/bpf/
-BPF [STORAGE & CGROUPS]
-M: Martin KaFai Lau <martin.lau@linux.dev>
-L: bpf@vger.kernel.org
-S: Maintained
-F: kernel/bpf/*storage.c
-F: kernel/bpf/bpf_lru*
-F: kernel/bpf/cgroup.c
-
BPF [TOOLING] (bpftool)
M: Quentin Monnet <qmo@kernel.org>
L: bpf@vger.kernel.org
--
2.53.0-Meta
next reply other threads:[~2026-05-29 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:39 Martin KaFai Lau [this message]
2026-05-29 22:26 ` [PATCH bpf-next] bpf: MAINTAINERS: Update bpf maintainers Daniel Borkmann
2026-05-30 1:35 ` Jason Xing
2026-05-30 2:57 ` Martin KaFai Lau
2026-05-30 3:32 ` Jason Xing
2026-05-30 4:57 ` Jiayuan Chen
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=20260529203909.1222164-1-martin.lau@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
/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