From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Luke Nelson <lukenels@cs.washington.edu>
Cc: bpf@vger.kernel.org, "Luke Nelson" <luke.r.nels@gmail.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Martin KaFai Lau" <kafai@fb.com>,
"Song Liu" <songliubraving@fb.com>, "Yonghong Song" <yhs@fb.com>,
"Andrii Nakryiko" <andriin@fb.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Albert Ou" <aou@eecs.berkeley.edu>,
"Björn Töpel" <bjorn.topel@gmail.com>,
"Xi Wang" <xi.wang@gmail.com>,
"Mauro Carvalho Chehab" <mchehab+samsung@kernel.org>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Rob Herring" <robh@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, linux-riscv@lists.infradead.org
Subject: Re: [PATCH bpf-next v4 4/4] MAINTAINERS: Add entry for RV32G BPF JIT
Date: Tue, 3 Mar 2020 12:02:28 +0200 [thread overview]
Message-ID: <20200303100228.GJ1224808@smile.fi.intel.com> (raw)
In-Reply-To: <20200303005035.13814-5-luke.r.nels@gmail.com>
On Mon, Mar 02, 2020 at 04:50:35PM -0800, Luke Nelson wrote:
Commit message?
> Cc: Björn Töpel <bjorn.topel@gmail.com>
> Signed-off-by: Xi Wang <xi.wang@gmail.com>
> Signed-off-by: Luke Nelson <luke.r.nels@gmail.com>
> @@ -3213,11 +3213,20 @@ L: bpf@vger.kernel.org
> S: Maintained
> F: arch/powerpc/net/
>
> -BPF JIT for RISC-V (RV64G)
> +BPF JIT for 32-bit RISC-V (RV32G)
> +M: Luke Nelson <luke.r.nels@gmail.com>
> +M: Xi Wang <xi.wang@gmail.com>
> +L: bpf@vger.kernel.org
> +S: Maintained
> +F: arch/riscv/net/
> +X: arch/riscv/net/bpf_jit_comp.c
> +
> +BPF JIT for 64-bit RISC-V (RV64G)
> M: Björn Töpel <bjorn.topel@gmail.com>
> -L: netdev@vger.kernel.org
> +L: bpf@vger.kernel.org
> S: Maintained
> F: arch/riscv/net/
> +X: arch/riscv/net/bpf_jit_comp32.c
Obviously this breaks an order. Please, fix.
Hint: run parse-maintainers.pl after the change.
> BPF JIT for S390
> M: Ilya Leoshkevich <iii@linux.ibm.com>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-03-03 10:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 0:50 [PATCH bpf-next v4 0/4] eBPF JIT for RV32G Luke Nelson
2020-03-03 0:50 ` [PATCH bpf-next v4 1/4] riscv, bpf: move common riscv JIT code to header Luke Nelson
2020-03-03 7:50 ` Björn Töpel
2020-03-04 2:31 ` Luke Nelson
2020-03-04 5:44 ` Björn Töpel
2020-03-03 0:50 ` [PATCH bpf-next v4 2/4] riscv, bpf: add RV32G eBPF JIT Luke Nelson
2020-03-03 7:48 ` Björn Töpel
2020-03-04 2:32 ` Luke Nelson
2020-03-04 5:59 ` Björn Töpel
2020-03-04 7:24 ` Luke Nelson
2020-03-04 7:31 ` Björn Töpel
2020-03-03 0:50 ` [PATCH bpf-next v4 3/4] bpf, doc: add BPF JIT for RV32G to BPF documentation Luke Nelson
2020-03-03 7:27 ` Björn Töpel
2020-03-03 0:50 ` [PATCH bpf-next v4 4/4] MAINTAINERS: Add entry for RV32G BPF JIT Luke Nelson
2020-03-03 5:51 ` Björn Töpel
2020-03-03 10:02 ` Andy Shevchenko [this message]
2020-03-04 2:33 ` Luke Nelson
2020-03-04 10:21 ` Andy Shevchenko
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=20200303100228.GJ1224808@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriin@fb.com \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--cc=bjorn.topel@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=kafai@fb.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=luke.r.nels@gmail.com \
--cc=lukenels@cs.washington.edu \
--cc=mchehab+samsung@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=songliubraving@fb.com \
--cc=stephen@networkplumber.org \
--cc=xi.wang@gmail.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).