From: "Tobin C. Harding" <me@tobin.cc>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
"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: Re: [PATCH bpf-next 0/4] Convert filter.txt to RST
Date: Sat, 11 Aug 2018 07:54:12 +1000 [thread overview]
Message-ID: <20180810215412.GM32374@eros> (raw)
In-Reply-To: <20180810065752.2ab5473d@lwn.net>
On Fri, Aug 10, 2018 at 06:57:52AM -0600, Jonathan Corbet wrote:
> On Fri, 10 Aug 2018 11:46:36 +1000
> "Tobin C. Harding" <me@tobin.cc> wrote:
>
> > Thanks for clarifying. My understanding is now; this is a case where
> > checkpatch is too verbose and we do not actually need to add a specific
> > license identifier to the documentation files (new or otherwise). They
> > get an implicit GPLv2.
>
> The objective actually is to have SPDX tags in all files in the kernel.
> That includes documentation, even though people, as always, care less
> about the docs than they do the code.
>
> As I understood it, the complaint with the tags you put in wasn't their
> existence, it was your putting GPLv2+ rather than straight GPLv2. In the
> absence of information to the contrary, you really have to assume the
> latter, since that's the overall license for the kernel.
Righto, thanks Jon. GPLv0 tags going in for v3
Tobin
prev parent reply other threads:[~2018-08-10 21:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 5:23 [PATCH bpf-next 0/4] Convert filter.txt to RST Tobin C. Harding
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 [this message]
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=20180810215412.GM32374@eros \
--to=me@tobin.cc \
--cc=alexei.starovoitov@gmail.com \
--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).