From: Emil Tsalapatis <emil@etsalapatis.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, memxor@gmail.com,
daniel@iogearbox.net, eddyz87@gmail.com,
Emil Tsalapatis <emil@etsalapatis.com>
Subject: [PATCH bpf-next] MAINTAINERS: BPF: Add self as reviewer and run parse_maintainers.pl
Date: Thu, 4 Jun 2026 14:42:52 -0400 [thread overview]
Message-ID: <20260604184252.9917-1-emil@etsalapatis.com> (raw)
Add myself as a reviewer for the BPF subsystem. While at it, run
./scripts/parse_maintainers.pl --order and reorder the BPF-related
entries in the file accordingly.
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
MAINTAINERS | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index afae76600fc6..87ac5cafb55b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4811,12 +4811,13 @@ BPF [GENERAL] (Safe Dynamic Programs and Tools)
M: Alexei Starovoitov <ast@kernel.org>
M: Daniel Borkmann <daniel@iogearbox.net>
M: Andrii Nakryiko <andrii@kernel.org>
-R: Martin KaFai Lau <martin.lau@linux.dev>
M: Eduard Zingerman <eddyz87@gmail.com>
M: Kumar Kartikeya Dwivedi <memxor@gmail.com>
+R: Martin KaFai Lau <martin.lau@linux.dev>
R: Song Liu <song@kernel.org>
R: Yonghong Song <yonghong.song@linux.dev>
R: Jiri Olsa <jolsa@kernel.org>
+R: Emil Tsalapatis <emil@etsalapatis.com>
L: bpf@vger.kernel.org
S: Supported
W: https://bpf.io/
@@ -4826,7 +4827,9 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
F: Documentation/bpf/
F: Documentation/networking/filter.rst
F: Documentation/userspace-api/ebpf/
+F: arch/*/include/asm/rqspinlock.h
F: arch/*/net/*
+F: include/asm-generic/rqspinlock.h
F: include/linux/bpf*
F: include/linux/btf*
F: include/linux/buildid.h
@@ -4838,17 +4841,15 @@ F: include/uapi/linux/filter.h
F: kernel/bpf/
F: kernel/trace/bpf_trace.c
F: lib/buildid.c
-F: arch/*/include/asm/rqspinlock.h
-F: include/asm-generic/rqspinlock.h
F: lib/test_bpf.c
F: net/bpf/
F: net/core/filter.c
F: net/sched/act_bpf.c
F: net/sched/cls_bpf.c
F: samples/bpf/
+F: scripts/Makefile.btf
F: scripts/bpf_doc.py
F: scripts/gen-btf.sh
-F: scripts/Makefile.btf
F: scripts/pahole-version.sh
F: tools/bpf/
F: tools/lib/bpf/
--
2.54.0
next reply other threads:[~2026-06-04 18:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 18:42 Emil Tsalapatis [this message]
2026-06-04 18:44 ` [PATCH bpf-next] MAINTAINERS: BPF: Add self as reviewer and run parse_maintainers.pl Eduard Zingerman
2026-06-04 19:55 ` Kumar Kartikeya Dwivedi
2026-06-05 14:53 ` Jiri Olsa
2026-06-05 15:10 ` 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=20260604184252.9917-1-emil@etsalapatis.com \
--to=emil@etsalapatis.com \
--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 \
/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