linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/4] Convert filter.txt to RST
Date: Thu,  9 Aug 2018 15:23:24 +1000	[thread overview]
Message-ID: <20180809052328.27942-1-me@tobin.cc> (raw)

Hi,

This is my latest attempt at converting Documentation/filter.txt to RST
format.  Added to the CC list because of additional changes to
Documentation/userspace-api/seccomp_filter.rst

For reference this set is a progression of the follow sets (in order of
post date to LKML)

 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

Sending this to BPF maintainers for hopeful inclusion in the bpf-next
tree.  As discussed on LKML this set does all the conversion in a single
patch.  This includes adding SPDX licence comments
(inc. seccomp_filter), adding RST labels, and updating references.

Please note this set adds three files to the MAINTAINERS file for the
BPF maintainers.  Is this rude?

Also this set adds a SPDX licence to all new files and also to
seccomp_filter.rst  I did this because checkpatch asked me to but I am
unsure on the protocol, is it acceptable to add a licence to
documentation that someone else wrote?

For the Record;

Daniel and Alexei, can I please have permission to add GPLv2+ to the BPF
docs?

Kees, Andy, and Drewry, can I please have permission to add GPLv2+ to
seccomp_filter.rst 

(added Cc: tag to patch 2 that adds the licence identifiers)

thanks,
Tobin.

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/networking/filter.txt           | 1476 -----------------
 Documentation/userspace-api/cBPF.rst          |  432 +++++
 Documentation/userspace-api/eBPF.rst          | 1006 +++++++++++
 Documentation/userspace-api/index.rst         |    3 +
 .../userspace-api/seccomp_filter.rst          |   11 +
 Documentation/userspace-api/socket_filter.rst |  183 ++
 MAINTAINERS                                   |    4 +-
 7 files changed, 1638 insertions(+), 1477 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


             reply	other threads:[~2018-08-09  5:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-09  5:23 Tobin C. Harding [this message]
2018-08-09  5:23 ` [PATCH bpf-next 1/4] docs: net: Fix various minor typos Tobin C. Harding
2018-08-09  5:23 ` [PATCH bpf-next 2/4] docs: Separate and convert filter.txt to RST Tobin C. Harding
2018-08-09  5:23 ` [PATCH bpf-next 3/4] docs: Judiciously use double ticks Tobin C. Harding
2018-08-09  5:23 ` [PATCH bpf-next 4/4] docs: Remove filter.txt from the tree Tobin C. Harding
2018-08-09  6:07 ` [PATCH bpf-next 0/4] Convert filter.txt to RST Alexei Starovoitov
2018-08-09  7:27   ` Tobin C. Harding
2018-08-09  8:24     ` Daniel Borkmann
2018-08-10  1:46       ` Tobin C. Harding
2018-08-10 12:57         ` Jonathan Corbet
2018-08-10 17:51           ` Alexei Starovoitov
2018-08-11 11:50             ` Tobin C. Harding
2018-08-13 19:37               ` Alexei Starovoitov
2018-08-10 21:54           ` 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=20180809052328.27942-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).