From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
iovisor-dev <iovisor-dev@lists.iovisor.org>,
Wang Nan <wangnan0@huawei.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Richard Henderson <rth@twiddle.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Brendan Gregg <brendan.d.gregg@gmail.com>,
Brenden Blanco <bblanco@plumgrid.com>
Subject: headsup: llvm now uses official bpf e_machine value
Date: Fri, 15 Jul 2016 16:08:31 -0700 [thread overview]
Message-ID: <CAADnVQ+nuswu1kC2ae_4-pZve-u1tL5JsOx1e2QbTO4ozyOh7Q@mail.gmail.com> (raw)
just pushed Richard's patch
https://github.com/llvm-mirror/llvm/commit/36b9c09330bfb5e771914cfe307588f30d5510d2
tested with bcc and different bpf loaders.
Thankfully none of them rely on old and arguably
buggy em_none value, so no breakage expected.
if you're using special bpf elf loader, please test.
Thanks
reply other threads:[~2016-07-15 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAADnVQ+nuswu1kC2ae_4-pZve-u1tL5JsOx1e2QbTO4ozyOh7Q@mail.gmail.com \
--to=alexei.starovoitov@gmail.com \
--cc=acme@kernel.org \
--cc=bblanco@plumgrid.com \
--cc=brendan.d.gregg@gmail.com \
--cc=daniel@iogearbox.net \
--cc=iovisor-dev@lists.iovisor.org \
--cc=netdev@vger.kernel.org \
--cc=rth@twiddle.net \
--cc=wangnan0@huawei.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).