All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	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: Re: [PATCH bpf-next 0/4] Convert filter.txt to RST
Date: Wed, 8 Aug 2018 23:07:35 -0700	[thread overview]
Message-ID: <20180809060734.rtqqu4sexbwzuqmm@ast-mbp> (raw)
In-Reply-To: <20180809052328.27942-1-me@tobin.cc>

On Thu, Aug 09, 2018 at 03:23:24PM +1000, Tobin C. Harding wrote:
> 
> Daniel and Alexei, can I please have permission to add GPLv2+ to the BPF
> docs?

kernel licensing is GPLv2 without +
every file (including docs) can potentially have a different
compatible license, but since they were developed
implicitly under v2 only you would need to get a buy-in from
all contributors before making such change.


WARNING: multiple messages have this Message-ID (diff)
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
	Alexei Starovoitov <ast@kernel.org>,
	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: Re: [PATCH bpf-next 0/4] Convert filter.txt to RST
Date: Wed, 8 Aug 2018 23:07:35 -0700	[thread overview]
Message-ID: <20180809060734.rtqqu4sexbwzuqmm@ast-mbp> (raw)
In-Reply-To: <20180809052328.27942-1-me@tobin.cc>

On Thu, Aug 09, 2018 at 03:23:24PM +1000, Tobin C. Harding wrote:
> 
> Daniel and Alexei, can I please have permission to add GPLv2+ to the BPF
> docs?

kernel licensing is GPLv2 without +
every file (including docs) can potentially have a different
compatible license, but since they were developed
implicitly under v2 only you would need to get a buy-in from
all contributors before making such change.

--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2018-08-09  6:07 UTC|newest]

Thread overview: 22+ 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 ` 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   ` 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   ` 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   ` 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  5:23   ` Tobin C. Harding
2018-08-09  6:07 ` Alexei Starovoitov [this message]
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  7:27     ` Tobin C. Harding
2018-08-09  8:24     ` Daniel Borkmann
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=20180809060734.rtqqu4sexbwzuqmm@ast-mbp \
    --to=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=me@tobin.cc \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.