From: Dave Airlie <airlied@linux.ie>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
linux-kernel@vger.kernel.org, adaplas@pol.net
Subject: Re: nvidia fb licensing issue.
Date: Tue, 15 Mar 2005 10:32:35 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.58.0503151028160.22756@skynet> (raw)
In-Reply-To: <9e47339105031318038d74da9@mail.gmail.com>
On Sun, 13 Mar 2005, Jon Smirl wrote:
> All of the files in drivers/char/drm really should have an explicit
> dual MIT/GPL license on them too. The DRM project has been taking
> patches back into DRM from LKML without making it clear that DRM is
> MIT licensed. It might be construed that doing this has made DRM GPL
> without that being the intention.
They all have explicit MIT licenses on them, these files are only
dual-licensed by the fact that they are shipped with the kernel, but they
are MIT licensed and I would consider any changes to them to be MIT
licensed unless someone explicitly states it..
Similiar to the reiser notice on top of those files.. I think MIT license
is explicit enough...
Some files are GPL licensed like drm_sysfs as it is obivously derived from
GPL code,
Dave.
--
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG
next prev parent reply other threads:[~2005-03-15 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-13 4:24 Dave Jones
2005-03-13 5:59 ` Andrew Morton
2005-03-13 8:18 ` Arjan van de Ven
2005-03-14 2:03 ` Jon Smirl
2005-03-14 6:53 ` Arjan van de Ven
2005-03-15 10:32 ` Dave Airlie [this message]
2005-03-15 11:06 ` Arjan van de Ven
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=Pine.LNX.4.58.0503151028160.22756@skynet \
--to=airlied@linux.ie \
--cc=adaplas@pol.net \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®