public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <002a01c62aeb$30c55e00$1001a8c0@kalmiopsis> (raw)
In-Reply-To: <20060205192025.4006a554.akpm@osdl.org>

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>


      parent reply	other threads:[~2006-02-06  7:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1139154997.14624.20.camel@localhost.localdomain>
2006-02-06  3:20 ` [Fwd: [PATCH 8/12] LED: Add LED device support for ixp4xx devices] Andrew Morton
2006-02-06  3:41   ` Felipe W Damasio
2006-02-06  4:19   ` Linus Torvalds
2006-02-06  5:07   ` Arjan van de Ven
2006-02-06  7:00     ` Dan McDonald
2006-02-06 13:56       ` Arjan van de Ven
2006-02-06  7:01   ` John Bowler [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='002a01c62aeb$30c55e00$1001a8c0@kalmiopsis' \
    --to=jbowler@acm.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rpurdie@rpsys.net \
    /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