From: Daniel Borkmann <daniel@iogearbox.net>
To: Shubham Bansal <illusionist.neo@gmail.com>, davem@davemloft.net
Cc: netdev@vger.kernel.org, ast@fb.com
Subject: Re: [PATCH net-next] bpf, doc: Add arm32 as arch supporting eBPF JIT
Date: Wed, 23 Aug 2017 19:03:15 +0200 [thread overview]
Message-ID: <599DB553.4060609@iogearbox.net> (raw)
In-Reply-To: <1503503950-5146-1-git-send-email-illusionist.neo@gmail.com>
On 08/23/2017 05:59 PM, 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: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2017-08-23 17:03 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
2017-08-23 17:03 ` Daniel Borkmann [this message]
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=599DB553.4060609@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--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).