From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH 6/6] src/uapi/wireguard: add SPDX tag
Date: Fri, 1 Dec 2017 09:43:46 +0000 [thread overview]
Message-ID: <20171201094346.GC9353@kroah.com> (raw)
In-Reply-To: <CAHmME9qp623Fx4U+4-Q2DreXJn+aXz_ecfruxi16Szjpwgq9cg@mail.gmail.com>
On Thu, Nov 30, 2017 at 07:02:24PM +0100, Jason A. Donenfeld wrote:
> On Thu, Nov 30, 2017 at 4:23 PM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > Update the wireguard.h file with the currently convential GPL2+userspace
> > exception tag.
> >
> > Note, this is a different license than what the text itself says in the
> > file, if you wish to stick with the MIT license for this file, that's
> > fine, but then it should be listed as:
> > ((GPL-2.0 WITH Linux-syscall-note) OR MIT)
>
> I'd prefer doing only "GPL-2.0 WITH Linux-syscall-note", since it's
> more uniform, but I don't know if it covers a particular use use case:
>
> I expect for many projects to wholesale copy and paste this file into
> their own projects, and those projects might not be GPL-friendly. Does
> the Linux-syscall-note allow for that? Or should I stick with
> GPL-2.0||MIT for the avoidance of doubt?
I think if you want others to be able to copy the file into different
projects without any doubt at all, stick to:
((GPL-2.0 WITH Linux-syscall-note) OR MIT)
as that covers everything.
> In terms of "intellectual property", the file itself is extremely
> boring, just defining some enums.
I'm not going to get into the argument of what is, and is not, a
copyrightable work :)
But to be safe, put this on the top so that everyone knows your
intention, which is the most important thing of all, as intent matters a
lot to companies and to courts.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-01 9:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 15:23 [PATCH 0/6] wireguard: add SPDX tags Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 1/6] src/tools: add SPDX tags to all files Greg Kroah-Hartman
2017-11-30 17:57 ` Jason A. Donenfeld
2017-11-30 23:49 ` Jason A. Donenfeld
2017-12-01 9:41 ` Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 2/6] src/selftest: " Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 3/6] src/tests: " Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 4/6] src/crypto: " Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 5/6] src: " Greg Kroah-Hartman
2017-11-30 15:23 ` [PATCH 6/6] src/uapi/wireguard: add SPDX tag Greg Kroah-Hartman
2017-11-30 18:02 ` Jason A. Donenfeld
2017-12-01 9:43 ` Greg Kroah-Hartman [this message]
2017-11-30 17:54 ` [PATCH 0/6] wireguard: add SPDX tags Jason A. Donenfeld
2017-12-03 15:13 ` Jason A. Donenfeld
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=20171201094346.GC9353@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jason@zx2c4.com \
--cc=wireguard@lists.zx2c4.com \
/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).