From: Daniel Borkmann <dborkman@redhat.com>
To: davem@davemloft.net
Cc: ast@plumgrid.com, netdev@vger.kernel.org
Subject: [PATCH net-next 0/2] Update BPF documentation
Date: Tue, 10 Jun 2014 17:44:05 +0200 [thread overview]
Message-ID: <1402415047-13535-1-git-send-email-dborkman@redhat.com> (raw)
This set contains some important updates on the BPF documentation.
I have rebased the set on top of the pending rename in [1] that
touches one line from the doc as well, but actually there shouldn't
be conflicts either way. If so nevertheless, please let me know.
Thanks!
[1] http://patchwork.ozlabs.org/patch/357025/
Alexei Starovoitov (2):
net: filter: mention eBPF terminology as well
net: filter: document internal instruction encoding
Documentation/networking/filter.txt | 246 ++++++++++++++++++++++++++++++------
1 file changed, 204 insertions(+), 42 deletions(-)
--
1.7.11.7
next reply other threads:[~2014-06-10 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 15:44 Daniel Borkmann [this message]
2014-06-10 15:44 ` [PATCH net-next 1/2] net: filter: mention eBPF terminology as well Daniel Borkmann
2014-06-10 15:44 ` [PATCH net-next 2/2] net: filter: document internal instruction encoding Daniel Borkmann
2014-06-11 22:40 ` [PATCH net-next 0/2] Update BPF documentation 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=1402415047-13535-1-git-send-email-dborkman@redhat.com \
--to=dborkman@redhat.com \
--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).