From: patchwork-bot+netdevbpf@kernel.org
To: Pu Lehui <pulehui@huaweicloud.com>
Cc: bjorn@kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com,
pjw@kernel.org, palmer@dabbelt.com, luke.r.nels@gmail.com,
xi.wang@gmail.com, bpf@vger.kernel.org,
linux-riscv@lists.infradead.org, pulehui@huawei.com
Subject: Re: [PATCH bpf] MAINTAINERS: Add myself as co-maintainer of riscv bpf
Date: Sun, 11 Oct 2026 13:40:13 +0000 [thread overview]
Message-ID: <179172601303.2055679.524571324990468455.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260930104659.1919027-1-pulehui@huaweicloud.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 30 Sep 2026 10:46:59 +0000 you wrote:
> From: Pu Lehui <pulehui@huawei.com>
>
> Over the years, I have been actively involved in the development and
> have proactively taken on maintenance responsibilities for the RV64 JIT,
> covering the related bpf core, riscv architecture, and selftests/CI
> infrastructure. With the continuous growth of riscv bpf features and
> testing workload, adding a co-maintainer helps share the review burden
> and ensure timely patch handling.
>
> [...]
Here is the summary with links:
- [bpf] MAINTAINERS: Add myself as co-maintainer of riscv bpf
https://git.kernel.org/bpf/bpf-next/c/10aaef818b15
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2026-10-11 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:46 [PATCH bpf] MAINTAINERS: Add myself as co-maintainer of riscv bpf Pu Lehui
2026-09-30 12:32 ` Björn Töpel
2026-10-11 13:40 ` patchwork-bot+netdevbpf [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=179172601303.2055679.524571324990468455.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=memxor@gmail.com \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=pulehui@huawei.com \
--cc=pulehui@huaweicloud.com \
--cc=xi.wang@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