linux-kernel - Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3

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:	Sun, 10 Jun 2007 11:03:30 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	Tarkan Erimer <tarkan@...one.net.tr>
cc:	davids@...master.com, linux-kernel@...r.kernel.org
Subject: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3


On Jun 10 2007 11:37, Tarkan Erimer wrote:
>
> Thanks for the corrections ;-) The whole picture is more clear now for me :-)
> BTW,I found a really interesting blog entry about which code in Linux Kernel is
> using which version of GPL :
>
> http://6thsenseless.blogspot.com/2007/02/how-much-linux-kernel-code-is-gpl-2.html

You've got to take MODULE_LICENSE() into account. There is

	MODULE_LICENSE("GPL");
	MODULE_LICENSE("GPL v2");
	MODULE_LICENSE("GPL and additional rights");
	MODULE_LICENSE("Dual BSD/GPL");
	MODULE_LICENSE("Dual MIT/GPL");
	MODULE_LICENSE("Dual MPL/GPL");

I think it's time to set things right, making

	* MODULE_LICENSE the authoritative place for the license
	  (also makes it easier to grep for)

	* sync up license into MODULE_LICENSE



	Jan
-- 
-
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/