From: Pu Lehui <pulehui@huawei.com>
To: "Björn Töpel" <bjorn@kernel.org>, "Puranjay Mohan" <puranjay@kernel.org>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"John Fastabend" <john.fastabend@gmail.com>,
"Björn Töpel" <bjorn@rivosinc.com>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
linux-riscv@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH bpf] MAINTAINERS: bpf: Add Lehui and Puranjay as riscv64 reviewers
Date: Sun, 7 Apr 2024 09:47:35 +0800 [thread overview]
Message-ID: <959db176-a79e-4074-a4bb-d9ee5ce19f79@huawei.com> (raw)
In-Reply-To: <20240405123352.2852393-1-bjorn@kernel.org>
On 2024/4/5 20:33, Björn Töpel wrote:
> From: Björn Töpel <bjorn@rivosinc.com>
>
> Lehui and Puranjay have been active RISC-V 64-bit BPF JIT
> contributors/reviewers for a long time!
>
> Let's make it more official by adding them as reviewers in
> MAINTAINERS.
It's my honor to take on this responsibility, and delighted to be
partnered with you Björn and Puranjay.😀
Lehui
>
> Thank you for your hard work!
>
> Signed-off-by: Björn Töpel <bjorn@kernel.org>
> ---
> MAINTAINERS | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 75381386fe4c..58ab032ad33d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3764,6 +3764,8 @@ X: arch/riscv/net/bpf_jit_comp64.c
>
> BPF JIT for RISC-V (64-bit)
> M: Björn Töpel <bjorn@kernel.org>
> +R: Pu Lehui <pulehui@huawei.com>
> +R: Puranjay Mohan <puranjay@kernel.org>
> L: bpf@vger.kernel.org
> S: Maintained
> F: arch/riscv/net/
>
> base-commit: c88b9b4cde17aec34fb9bfaf69f9f72a1c44f511
prev parent reply other threads:[~2024-04-07 1:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-05 12:33 [PATCH bpf] MAINTAINERS: bpf: Add Lehui and Puranjay as riscv64 reviewers Björn Töpel
2024-04-05 17:40 ` patchwork-bot+netdevbpf
2024-04-07 1:47 ` Pu Lehui [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=959db176-a79e-4074-a4bb-d9ee5ce19f79@huawei.com \
--to=pulehui@huawei.com \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn@kernel.org \
--cc=bjorn@rivosinc.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=puranjay@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