linux-kernel - [PATCH bpf-next 0/4] Convert filter.txt to RST

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20180809052328.27942-1-me@tobin.cc>
Date:   Thu,  9 Aug 2018 15:23:24 +1000
From:   "Tobin C. Harding" <me@...in.cc>
To:     Daniel Borkmann <daniel@...earbox.net>,
        Alexei Starovoitov <ast@...nel.org>
Cc:     "Tobin C. Harding" <me@...in.cc>, Jonathan Corbet <corbet@....net>,
        "David S. Miller" <davem@...emloft.net>,
        Kees Cook <keescook@...omium.org>,
        Andy Lutomirski <luto@...capital.net>,
        Will Drewry <wad@...omium.org>, linux-doc@...r.kernel.org,
        netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: [PATCH bpf-next 0/4] Convert filter.txt to RST

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