From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Martin KaFai Lau <martin.lau@linux.dev>, 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: Re: [PATCH bpf-next] bpf: MAINTAINERS: Update bpf maintainers
Date: Sat, 30 May 2026 12:57:42 +0800 [thread overview]
Message-ID: <67ad3005-f515-4ac6-840d-ded8c2e765b5@linux.dev> (raw)
In-Reply-To: <20260529203909.1222164-1-martin.lau@linux.dev>
On 5/30/26 4:39 AM, Martin KaFai Lau wrote:
> 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!
Thank you Martin, and best wishes for your long break.
I really appreciate all your guidance and help over the years.
My first kernel commit was guided by you, and I am still very grateful
for that.
Thanks again, and take care!
prev parent reply other threads:[~2026-05-30 4:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 20:39 [PATCH bpf-next] bpf: MAINTAINERS: Update bpf maintainers Martin KaFai Lau
2026-05-29 22:26 ` 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 [this message]
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=67ad3005-f515-4ac6-840d-ded8c2e765b5@linux.dev \
--to=jiayuan.chen@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=martin.lau@linux.dev \
--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