From: Daniel Borkmann <daniel@iogearbox.net>
To: Alexei Starovoitov <ast@fb.com>,
"David S . Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] samples/bpf: fix bpf loader
Date: Wed, 23 Nov 2016 10:57:37 +0100 [thread overview]
Message-ID: <58356811.1070407@iogearbox.net> (raw)
In-Reply-To: <1479862329-2361912-2-git-send-email-ast@fb.com>
On 11/23/2016 01:52 AM, Alexei Starovoitov wrote:
> llvm can emit relocations into sections other than program code
> (like debug info sections). Ignore them during parsing of elf file
>
> Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2016-11-23 9:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 0:52 [PATCH net-next 1/2] samples/bpf: fix sockex2 example Alexei Starovoitov
2016-11-23 0:52 ` [PATCH net-next 2/2] samples/bpf: fix bpf loader Alexei Starovoitov
2016-11-23 9:57 ` Daniel Borkmann [this message]
2016-11-24 21:05 ` David Miller
2016-11-23 9:58 ` [PATCH net-next 1/2] samples/bpf: fix sockex2 example Daniel Borkmann
2016-11-24 21:05 ` 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=58356811.1070407@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@fb.com \
--cc=davem@davemloft.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).