From: "Björn Töpel" <bjorn.topel@gmail.com>
To: Luke Nelson <lukenels@cs.washington.edu>
Cc: Song Liu <songliubraving@fb.com>,
linux-doc@vger.kernel.org, Yonghong Song <yhs@fb.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Alexei Starovoitov <ast@kernel.org>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
linux-riscv@lists.infradead.org, Rob Herring <robh@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jonathan Corbet <corbet@lwn.net>,
Jakub Kicinski <kuba@kernel.org>,
Andrii Nakryiko <andriin@fb.com>, Xi Wang <xi.wang@gmail.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Luke Nelson <luke.r.nels@gmail.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Martin KaFai Lau <kafai@fb.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Netdev <netdev@vger.kernel.org>, bpf <bpf@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH bpf-next v5 0/4] eBPF JIT for RV32G
Date: Thu, 5 Mar 2020 06:40:28 +0100 [thread overview]
Message-ID: <CAJ+HfNjrUxVqpBgC-WLHbZX7_7Gd-Lk7ghrmASTmaNySuXVUfg@mail.gmail.com> (raw)
In-Reply-To: <20200305050207.4159-1-luke.r.nels@gmail.com>
On Thu, 5 Mar 2020 at 06:02, Luke Nelson <lukenels@cs.washington.edu> wrote:
>
> This series adds an eBPF JIT for 32-bit RISC-V (RV32G) to the kernel,
> adapted from the RV64 JIT and the 32-bit ARM JIT.
>
Nice work! Thanks for hanging in there!
For the series,
Acked-by: Björn Töpel <bjorn.topel@gmail.com>
Reviewed-by: Björn Töpel <bjorn.topel@gmail.com>
next prev parent reply other threads:[~2020-03-05 5:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 5:02 [PATCH bpf-next v5 0/4] eBPF JIT for RV32G Luke Nelson
2020-03-05 5:02 ` [PATCH bpf-next v5 1/4] riscv, bpf: factor common RISC-V JIT code Luke Nelson
2020-03-05 5:02 ` [PATCH bpf-next v5 2/4] riscv, bpf: add RV32G eBPF JIT Luke Nelson
2020-03-05 5:02 ` [PATCH bpf-next v5 3/4] bpf, doc: add BPF JIT for RV32G to BPF documentation Luke Nelson
2020-03-05 5:02 ` [PATCH bpf-next v5 4/4] MAINTAINERS: add entry for RV32G BPF JIT Luke Nelson
2020-03-05 5:40 ` Björn Töpel [this message]
2020-03-05 15:19 ` [PATCH bpf-next v5 0/4] eBPF JIT for RV32G Daniel Borkmann
2020-03-05 15:53 ` Andy Shevchenko
2020-03-05 16:53 ` Björn Töpel
2020-03-05 22:46 ` Daniel Borkmann
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=CAJ+HfNjrUxVqpBgC-WLHbZX7_7Gd-Lk7ghrmASTmaNySuXVUfg@mail.gmail.com \
--to=bjorn.topel@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriin@fb.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=aou@eecs.berkeley.edu \
--cc=ast@kernel.org \
--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).