From: David Miller <davem@davemloft.net>
To: daniel@iogearbox.net
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] bpf, elf: add official ELF machine define for eBPF
Date: Wed, 20 Jul 2016 12:37:49 -0700 (PDT) [thread overview]
Message-ID: <20160720.123749.1466220963632605263.davem@davemloft.net> (raw)
In-Reply-To: <d7fb256f1011ef948809f1447f745da42da970a3.1469038166.git.daniel@iogearbox.net>
From: Daniel Borkmann <daniel@iogearbox.net>
Date: Wed, 20 Jul 2016 20:17:47 +0200
> Add the official BPF ELF e_machine value that was assigned recently [1,2]
> and will be propagated to glibc, et al. LLVM is switching to it in 3.9
> release.
>
> [1] https://github.com/llvm-mirror/llvm/commit/36b9c09330bfb5e771914cfe307588f30d5510d2
> [2] http://lists.iovisor.org/pipermail/iovisor-dev/2016-June/000266.html
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Acked-by: Alexei Starovoitov <ast@kernel.org>
Applied, thanks.
prev parent reply other threads:[~2016-07-20 19:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 18:17 [PATCH net-next] bpf, elf: add official ELF machine define for eBPF Daniel Borkmann
2016-07-20 19:37 ` David Miller [this message]
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=20160720.123749.1466220963632605263.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--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).