Reply-To: <jbowler@acm.org>
From: John Bowler <jbowler@acm.org>
To: "'Andrew Morton'" <akpm@osdl.org>, "'Richard Purdie'" <rpurdie@rpsys.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: [Fwd: [PATCH 8/12] LED: Add LED device support for ixp4xx devices]
Date: Sun, 5 Feb 2006 23:01:43 -0800
Message-ID: <002a01c62aeb$30c55e00$1001a8c0@kalmiopsis>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <20060205192025.4006a554.akpm@osdl.org>
Importance: Normal
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1185
Lines: 28

From: Andrew Morton [mailto:akpm@osdl.org]
>MIT license is unusual.  There's one other file in the kernel which uses it
>and that's down in MTD where nobody dares look.

Well, I look at the MTD code a lot... That's why I used it (i.e. that was the
existence proof I found that it's fine ;-)

>I don't know whether MIT is GPL-compatible-for-kernel-purposes or not.  Help.

Nothing it that license precludes the code being redistributed under the
GPL.  (It is a verbatim copy of
http://www.opensource.org/licenses/mit-license.php).

>MODULE_LICENSE("Dual MIT/GPL");

Is fine with me, indeed, given the license text, I don't believe I retain
any rights to *prevent* such a change (and it was certainly not my intent
to prevent redistribution under a more restrictive license).  Using 'MIT'
or substituting some more specific tag must be fine for the same reason
(it's a name of a license, not a license itself).

John Bowler <jbowler@acm.org>

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