From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Subject: GPLv2 or not GPLv2? (no license bashing)
Date: Thu, 4 Mar 2004 08:38:29 +0100 [thread overview]
Message-ID: <200403040838.31412.eike-kernel@sf-tec.de> (raw)
Hi all,
just digging a bit in the kernel and found some funny things:
-there is a tag only for "GPL v2" but there are some drivers claiming to be
v2 and not using this (patch will follow)
-there are some drivers with the comment ", either version 2 of the License."
in the header. s/either // ? If so, there are some more files where someone
should change MODULE_LICENSE("GPL") to "GPL v2".
-there are some files that have the long warranty warning in the header. This
brings up the question if we should see the mainline kernel as one piece of
software. If we do so we need this warning only once and this copy should be
in the main kernel directory and we should kill the others. The other
question is: when I only write down the names of the authors in the header
and then add MODULE_LICENSE("GPL") or "GPL v2" is this enough licensing
information or is always the long comment needed (would be another nice
trick to shrink tons of files)?
-the LINUX_VERSION_CODE line in drivers/message/fusion/isense.c looks bogus,
the comment says it is for <2.5.0, but the line itself is for <2.3.0. Is
this wanted (fix the comment), bogus (fix the line) or crap (kill it
alltogether).
This are the files where I found "either version 2 of the License.":
arch/arm/mach-integrator/integrator_cp.c
drivers/serial/8250_pnp.c
drivers/serial/8250_pci.c
drivers/input/serio/pcips2.c
drivers/input/serio/sa1111ps2.c
These are some files (there are surely tons of others) with the long warning:
drivers/scsi/3w-xxxx.[ch]
drivers/message/fusion/mptctl.c
drivers/message/fusion/mptbase.[ch]
drivers/message/fusion/mptscsih.c
drivers/message/fusion/isense.c (*)
drivers/message/fusion/mptlan.[ch]
drivers/message/fusion/mptctl.[ch]
drivers/message/fusion/mptscsih.[ch]
Eike
next reply other threads:[~2004-03-04 13:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 7:38 Rolf Eike Beer [this message]
2004-03-04 7:44 ` [PATCH] Change "GPL" to "GPL v2" where files are GPLv2 Rolf Eike Beer
2004-03-04 7:44 ` [PATCH] Add missing "GPL" Rolf Eike Beer
2004-03-04 14:11 ` GPLv2 or not GPLv2? (no license bashing) Richard B. Johnson
2004-03-09 7:16 ` vda
2004-03-09 9:04 ` Måns Rullgård
2004-03-09 9:53 ` vda
2004-03-09 10:12 ` Måns Rullgård
2004-03-09 16:58 ` Jesse Pollard
2004-03-09 17:26 ` Måns Rullgård
2004-03-09 17:38 ` Jesse Pollard
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=200403040838.31412.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--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