From: Alexei Starovoitov <ast@fb.com>
To: Shubham Bansal <illusionist.neo@gmail.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <daniel@iogearbox.net>
Subject: Re: [PATCH net-next] bpf, doc: Add arm32 as arch supporting eBPF JIT
Date: Wed, 23 Aug 2017 09:55:14 -0700 [thread overview]
Message-ID: <3f9982db-ea0a-dc2a-99d0-3d147f48a591@fb.com> (raw)
In-Reply-To: <1503503950-5146-1-git-send-email-illusionist.neo@gmail.com>
On 8/23/17 8:59 AM, Shubham Bansal wrote:
> As eBPF JIT support for arm32 was added recently with
> commit 39c13c204bb1150d401e27d41a9d8b332be47c49, it seems appropriate to
> add arm32 as arch with support for eBPF JIT in bpf and sysctl docs as well.
>
> Signed-off-by: Shubham Bansal <illusionist.neo@gmail.com>
Acked-by: Alexei Starovoitov <ast@kernel.org>
next prev parent reply other threads:[~2017-08-23 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-23 15:59 [PATCH net-next] bpf, doc: Add arm32 as arch supporting eBPF JIT Shubham Bansal
2017-08-23 16:55 ` Alexei Starovoitov [this message]
2017-08-23 17:03 ` Daniel Borkmann
2017-08-24 5:41 ` David Miller
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=3f9982db-ea0a-dc2a-99d0-3d147f48a591@fb.com \
--to=ast@fb.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=illusionist.neo@gmail.com \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).