From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: ast@plumgrid.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/2] bpf misc update
Date: Fri, 29 May 2015 23:23:05 +0200 [thread overview]
Message-ID: <cover.1432912637.git.daniel@iogearbox.net> (raw)
Daniel Borkmann (2):
ebpf: allow bpf_ktime_get_ns_proto also for networking
ebpf: misc core cleanup
include/linux/bpf.h | 1 +
kernel/bpf/core.c | 73 ++++++++++++++++++++++++++++--------------------
kernel/bpf/helpers.c | 47 ++++++++++++++++++++-----------
kernel/trace/bpf_trace.c | 12 --------
net/core/filter.c | 2 ++
5 files changed, 75 insertions(+), 60 deletions(-)
--
1.9.3
next reply other threads:[~2015-05-29 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 21:23 Daniel Borkmann [this message]
2015-05-29 21:23 ` [PATCH net-next 1/2] ebpf: allow bpf_ktime_get_ns_proto also for networking Daniel Borkmann
2015-06-01 4:44 ` David Miller
2015-05-29 21:23 ` [PATCH net-next 2/2] ebpf: misc core cleanup Daniel Borkmann
2015-05-29 23:25 ` Alexei Starovoitov
2015-06-01 4:45 ` 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=cover.1432912637.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@plumgrid.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).