From: Jiayuan Chen <jiayuan.chen@linux.dev>
To: Jakub Sitnicki <jakub@cloudflare.com>, bpf@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
John Fastabend <john.fastabend@gmail.com>,
Martin KaFai Lau <martin.lau@linux.dev>
Subject: Re: [PATCH bpf] bpf: Add Jiayuan Chen to sockmap maintainers
Date: Tue, 12 May 2026 11:04:39 +0800 [thread overview]
Message-ID: <4469c765-e9ab-46c9-adc1-ff1b812bf1ad@linux.dev> (raw)
In-Reply-To: <20260511-sockmap-ktls-fix-1-v1-1-96ff8c1906e4@cloudflare.com>
On 5/11/26 8:10 PM, Jakub Sitnicki wrote:
> Nominate Jiayuan Chen for the sockmap co-maintainer. Jiayuan has been a
> regular contributor and reviewer for the sockmap and networking code.
>
> Since we are now down to just two maintainers, and John has to split his
> time between BPF core, BPF networking, and sockmap, having three
> maintainers again will help with the review load.
>
> Signed-off-by: Jakub Sitnicki<jakub@cloudflare.com>
Acked-by: Jiayuan Chen <jiayuan.chen@linux.dev>
Thanks for the nomination !
I’ve noticed more sockmap-related issues coming up recently, and I’ll
keep helping to track and review them.
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b2040011a386..dfc621ff629d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -4861,6 +4861,7 @@ F: kernel/bpf/*iter.c
> BPF [L7 FRAMEWORK] (sockmap)
> M: John Fastabend<john.fastabend@gmail.com>
> M: Jakub Sitnicki<jakub@cloudflare.com>
> +M: Jiayuan Chen<jiayuan.chen@linux.dev>
> L: netdev@vger.kernel.org
> L: bpf@vger.kernel.org
> S: Maintained
>
>
>
prev parent reply other threads:[~2026-05-12 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:10 [PATCH bpf] bpf: Add Jiayuan Chen to sockmap maintainers Jakub Sitnicki
2026-05-12 3:04 ` 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=4469c765-e9ab-46c9-adc1-ff1b812bf1ad@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=jakub@cloudflare.com \
--cc=john.fastabend@gmail.com \
--cc=martin.lau@linux.dev \
/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