linux-kernel - Re: writable limits to -next

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Oct 2009 01:35:11 +0100
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Jiri Slaby <jirislaby@...il.com>, linux-next@...r.kernel.org,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	James Morris <jmorris@...ei.org>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Eric Paris <eparis@...isplace.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: writable limits to -next

Hi,

BTW you may want to check if the current wording is correct:

Stephen Rothwell <sfr@...b.auug.org.au> writes:

> You will need to ensure that the patches/commits in your tree/series have
> been:
>      * submitted under GPL v2 (or later) and include the Contributor's
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

It's not ok to submit under e.g. GPL v3 only, I'd suggest "under GPL v2
and optionally other licence(s)" or something like that.

For example code under BSD-style licence (in addition to GPLv2) is
present in Linux, though I think any additional licence (the "later" as
in "GPL v2 or later", GPL v3, MS EULA etc.) is acceptable as long as it
is really additional, i.e., if one can ignore it and "use" GPLv2
exclusively.

IANAL of course.
-- 
Krzysztof Halasa
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/