mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Dave Airlie <airlied@linux.ie>
Cc: Jon Smirl <jonsmirl@gmail.com>, 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 12:06:38 +0100	[thread overview]
Message-ID: <1110884798.6290.46.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0503151028160.22756@skynet>

On Tue, 2005-03-15 at 10:32 +0000, Dave Airlie wrote:
> 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..

this is actually a bit of a legal iffy point here. People submit patches
to the kernel (which is GPL). In addition, while patches to gpl code are
gpl (by the gpl "derived works" clause), the MIT license has no such
requirement or even assumption on derived works so it's all quite iffy.
I strongly suggest you put the dual license header in those files to get
rid of the ambiguity..  as you said it's not really a big deal in that
the code already is dual licensed in effect; please consider making it
explicit, it solves a lot of ambiguity.



      reply	other threads:[~2005-03-15 11:06 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
2005-03-15 11:06         ` Arjan van de Ven [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=1110884798.6290.46.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=adaplas@pol.net \
    --cc=airlied@linux.ie \
    --cc=akpm@osdl.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®