From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Enrico Weigelt, metux IT consult" <metux@gmx.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] p9caps: add Plan9 capability devices
Date: Sat, 10 Feb 2018 18:03:52 +0000 [thread overview]
Message-ID: <20180210180352.GO30522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20180210165845.18852-1-metux@gmx.de>
On Sat, Feb 10, 2018 at 04:58:45PM +0000, Enrico Weigelt, metux IT consult wrote:
> From: "Enrico Weigelt, metux IT consult" <info@metux.net>
> +MODULE_LICENSE("GPLv3");
... which is incompatible with GPLv2. I'm not even going to look at that
thing - same as with proprietary code. You CAN'T combine any derivatives
of that code with the kernel. Not without GPL violation.
And yes, there is GPLv2-only code all over the place in Linux VFS (at
least), with at least some of the copyright holders not going to permit
violations of clause 6. Not going to happen.
If you want it in the kernel, you need a GPLv2-compatible license. GPLv3
does not qualify, and while it can be combined with GPLv2+ (yielding GPLv3
for combination), the kernel is not GPLv2+ - some parts are, but GPLv2-only
ones render the whole thing GPLv2-only.
prev parent reply other threads:[~2018-02-10 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 16:58 [PATCH] p9caps: add Plan9 capability devices Enrico Weigelt, metux IT consult
2018-02-10 17:54 ` Randy Dunlap
2018-02-11 21:50 ` Enrico Weigelt, metux IT consult
2018-02-11 21:50 ` [PATCH] " Enrico Weigelt, metux IT consult
2018-02-13 7:16 ` Serge E. Hallyn
2018-02-13 12:40 ` Enrico Weigelt, metux IT consult
2018-02-14 14:56 ` Serge E. Hallyn
2018-02-14 17:58 ` Enrico Weigelt
2018-02-17 22:11 ` Richard Weinberger
2018-04-25 10:38 ` Enrico Weigelt
2018-04-25 12:23 ` Richard Weinberger
2018-02-10 18:03 ` Al Viro [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=20180210180352.GO30522@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=metux@gmx.de \
/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