From: Stephen Hemminger <stephen@networkplumber.org>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: ast@kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next 0/2] BPF update
Date: Mon, 18 Jan 2016 11:43:53 -0800 [thread overview]
Message-ID: <20160118114353.36ab1fa7@xeon-e3> (raw)
In-Reply-To: <cover.1452559602.git.daniel@iogearbox.net>
On Tue, 12 Jan 2016 02:03:06 +0100
Daniel Borkmann <daniel@iogearbox.net> wrote:
> Two small BPF frontend updates.
>
> The patchset is against your current net-next branch (pre master merge).
>
> Thanks!
>
> Daniel Borkmann (2):
> tc, bpf: check section names and type everywhere
> tc, bpf: more header checks on loading elf
>
> tc/tc_bpf.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++------
> 1 file changed, 58 insertions(+), 6 deletions(-)
This applies fine to master. Accepted.
prev parent reply other threads:[~2016-01-18 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 1:03 [PATCH iproute2 -next 0/2] BPF update Daniel Borkmann
2016-01-12 1:03 ` [PATCH iproute2 -next 1/2] tc, bpf: check section names and type everywhere Daniel Borkmann
2016-01-12 1:03 ` [PATCH iproute2 -next 2/2] tc, bpf: more header checks on loading elf Daniel Borkmann
2016-01-18 19:43 ` Stephen Hemminger [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=20160118114353.36ab1fa7@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ast@kernel.org \
--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).