From: "Tobin C. Harding" <me@tobin.cc>
To: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>
Cc: "Tobin C. Harding" <me@tobin.cc>,
Jonathan Corbet <corbet@lwn.net>,
"David S. Miller" <davem@davemloft.net>,
Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH bpf-next v2 0/4] Convert filter.txt to RST
Date: Fri, 10 Aug 2018 12:24:46 +1000 [thread overview]
Message-ID: <20180810022450.1237-1-me@tobin.cc> (raw)
seccomp_filter.rst change removed from set, leaving CC list same as v1
for continuity.
Hi,
This is my latest attempt at converting Documentation/filter.txt to RST
format. This version removes the SPDX licence identifiers added in the
previous version.
This work has gotten a bit mixed up; for reference this set is a
progression of the follow sets (newest set last)
1. [PATCH bpf-next 00/13] docs: Convert BPF filter.txt to RST
2. [RFC bpf-next 0/3] docs: Convert filter.txt to RST
3. [RFC bpf-next v2 0/3] docs: Convert filter.txt to RST
4. [PATCH bpf-next 0/4] Convert filter.txt to RST
As discussed on LKML this set does all the conversion in a single
patch.
Please note this set adds three files to the MAINTAINERS file for the
BPF maintainers.
thanks,
Tobin.
v2:
- Remove SPDX licence identifiers
- Update old intree references to filter.txt
Tobin C. Harding (4):
docs: net: Fix various minor typos
docs: Separate and convert filter.txt to RST
docs: Judiciously use double ticks
docs: Remove filter.txt from the tree
Documentation/bpf/index.rst | 15 +-
Documentation/networking/00-INDEX | 2 -
Documentation/networking/filter.txt | 1476 -----------------
Documentation/networking/packet_mmap.txt | 2 +-
Documentation/userspace-api/cBPF.rst | 430 +++++
Documentation/userspace-api/eBPF.rst | 1004 +++++++++++
Documentation/userspace-api/index.rst | 3 +
.../userspace-api/seccomp_filter.rst | 9 +
Documentation/userspace-api/socket_filter.rst | 181 ++
MAINTAINERS | 4 +-
tools/bpf/bpf_asm.c | 6 +-
tools/bpf/bpf_dbg.c | 9 +-
12 files changed, 1653 insertions(+), 1488 deletions(-)
delete mode 100644 Documentation/networking/filter.txt
create mode 100644 Documentation/userspace-api/cBPF.rst
create mode 100644 Documentation/userspace-api/eBPF.rst
create mode 100644 Documentation/userspace-api/socket_filter.rst
--
2.17.1
next reply other threads:[~2018-08-10 2:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 2:24 Tobin C. Harding [this message]
2018-08-10 2:24 ` [PATCH bpf-next v2 1/4] docs: net: Fix various minor typos Tobin C. Harding
2018-08-10 2:24 ` [PATCH bpf-next v2 2/4] docs: Separate and convert filter.txt to RST Tobin C. Harding
2018-08-10 2:24 ` [PATCH bpf-next v2 3/4] docs: Judiciously use double ticks Tobin C. Harding
2018-08-10 2:24 ` [PATCH bpf-next v2 4/4] docs: Remove filter.txt from the tree Tobin C. Harding
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=20180810022450.1237-1-me@tobin.cc \
--to=me@tobin.cc \
--cc=ast@kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=keescook@chromium.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=netdev@vger.kernel.org \
--cc=wad@chromium.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).