linux-riscv.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Töpel" <bjorn.topel@gmail.com>
To: Daniel Borkmann <daniel@iogearbox.net>
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>,
	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>,
	Luke Nelson <lukenels@cs.washington.edu>,
	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 17:53:16 +0100	[thread overview]
Message-ID: <CAJ+HfNg_cP8DC+C0UGHnumde6+YhqBoTB909A9XwFMPv82tqWw@mail.gmail.com> (raw)
In-Reply-To: <4633123d-dc61-ab79-d2ee-e0cef66e4cea@iogearbox.net>

On Thu, 5 Mar 2020 at 16:19, Daniel Borkmann <daniel@iogearbox.net> wrote:
>
[...]
> Applied, thanks everyone!
>
> P.s.: I fixed the MAINTAINERS entry in the last one to have both netdev and bpf
> to be consistent with all the other JIT entries there.

Ah, I asked specifically Xi and Luke to *remove* the netdev entry, due
to the bpf_devel_QA.rst change. :-)


  parent reply	other threads:[~2020-03-05 16:53 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 ` [PATCH bpf-next v5 0/4] eBPF JIT for RV32G Björn Töpel
2020-03-05 15:19   ` Daniel Borkmann
2020-03-05 15:53     ` Andy Shevchenko
2020-03-05 16:53     ` Björn Töpel [this message]
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+HfNg_cP8DC+C0UGHnumde6+YhqBoTB909A9XwFMPv82tqWw@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).