linux-kernel - Re: [PATCH] module: Clarify GPL-Compatible is OK

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4F818952.3010609@broadcom.com>
Date:	Sun, 8 Apr 2012 14:49:22 +0200
From:	"Arend van Spriel" <arend@...adcom.com>
To:	"Alan Cox" <alan@...rguk.ukuu.org.uk>
cc:	"Luis R. Rodriguez" <mcgrof@...jolero.org>,
	"rusty@...tcorp.com.au" <rusty@...tcorp.com.au>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Keith Packard" <keithp@...thp.com>,
	"Ralf Baechle" <ralf@...ux-mips.org>,
	"David Woodhouse" <dwmw2@...radead.org>,
	"Stephen Hemminger" <shemminger@...tta.com>,
	"John W. Linville" <linville@...driver.com>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>,
	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
Subject: Re: [PATCH] module: Clarify GPL-Compatible is OK

On 04/07/2012 09:03 PM, Alan Cox wrote:
>> You do not need to make dual licenses when licenses are compatible
>> with each other, and in fact at times this can confuse developers / legal.
>
> Firstly you are out of order touching the licensing tags of other vendors
> code. Absolutely and utterly. So nobody should for example be touching an
> Intel MODULE_LICENSE() tag without the say so of Intel legal.

As the patch also includes driver code that Broadcom contributed to the 
kernel, I am inclined to agree. But to me it is not clear whether the 
MODULE_LICENSE() tag holds a true legal value. How does it relate to the 
legal disclaimer that is (probably) in each and every source file?

Gr. AvS

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