From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: GPL / MPL license issues.
Date: Tue, 7 Aug 2007 16:27:58 -0400 [thread overview]
Message-ID: <20070807202758.GA1937@redhat.com> (raw)
There are a number of files in the kernel that have in their
headers a notice that the file is under the Mozilla Public License,
which alone, is incompatible with the GPL.
This itself is fine, as long as the resulting code claims
to be Dual MPL/GPL, however there are a few cases where this
doesn't seem to be happening.
drivers/pcmcia/soc_common.c gets linked into
drivers/pcmcia/pxa2xx_core.o, which seems to end up with
a module license of "GPL".
ricoh.h and o2micro.h are MPL, yet get included in
drivers/pcmcia/yenta_socket.c which ends up as a "GPL" module.
drivers/pcmcia/i82365.h is MPL, yet gets included in the following
GPL only drivers ..
drivers/pcmcia/i82092.c
drivers/pcmcia/pd6729.c
drivers/pcmcia/vrc4171_card.c
drivers/pcmcia/yenta_socket.c
drivers/pcmcia/pd6729.c is MODULE_LICENSE("GPL"), yet includes
the MPL'd 'cirrus.h'
drivers/serial/serial_cs.c labels itself as MPL/GPL, yet
has a MODULE_LICENSE("GPL").
drivers/scsi/pcmcia/qlogic_stub.c does the same.
I may have missed some others, but this is what turned up from
some simple grepping.
I've got patches fixing up some of the simpler cases changing
the "GPL" to "Dual MPL/GPL", but I want to be sure I'm not
barking up the wrong tree first.
comments?
Dave
--
http://www.codemonkey.org.uk
next reply other threads:[~2007-08-07 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 20:27 Dave Jones [this message]
2007-08-07 21:26 ` Jeremy Maitin-Shepard
2008-08-02 12:58 Komuro
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=20070807202758.GA1937@redhat.com \
--to=davej@redhat.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®