From: Mark Hymers <markh@linuxfromscratch.org>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.17-pre1
Date: Thu, 29 Nov 2001 00:05:09 +0000 [thread overview]
Message-ID: <20011129000509.A1362@markcomp.blaydon.hymers.org.uk> (raw)
In-Reply-To: <E169EIY-0006UI-00@the-village.bc.nu> <1006991294.813.0.camel@phantasy>
In-Reply-To: <1006991294.813.0.camel@phantasy>; from rml@tech9.net on Wed, Nov 28, 2001 at 06:48:13PM -0500
On Wed, 28, Nov, 2001 at 06:48:13PM -0500, Robert Love spoke thus..
> On Wed, 2001-11-28 at 18:39, Alan Cox wrote:
> > > use "BSD without advertising clause", which causes the kernel to
> > > be
> > > tainted. Shouldn't fs/nls/*.c use "Dual BSD/GPL" or "GPL" instead?
> >
> > Dual BSD/GPL is the correct one. Not a big issue. Since the GPL
> > allows
> > stuff to be freer than GPL but still GPL its arguably correct too I
> > suspect
>
> I was waiting for confirmation about the license status...without
> getting into what license is correct and legal, the current
> MODULE_LICENSE value taints the kernel. The attached patch switches
> to
> Dual BSD/GPL.
Do you know what the legal status of the rest of the *.c files in fs/nls
is? There are still quite a few which have no MODULE_LICENSE tag at all
which causes the kernel to be tainted (IMO) incorrectly.
Mark
--
Mark Hymers BLFS Editor
markh@linuxfromscratch.org
next prev parent reply other threads:[~2001-11-29 0:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 22:00 Mikael Pettersson
2001-11-28 23:39 ` Alan Cox
2001-11-28 23:48 ` Robert Love
2001-11-29 0:05 ` Mark Hymers [this message]
2001-11-29 0:06 ` Robert Love
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 15:47 Marcelo Tosatti
2001-11-28 18:38 ` Andrey Nekrasov
2001-11-28 17:38 ` Marcelo Tosatti
2001-11-28 19:19 ` Tommy Reynolds
2001-11-29 2:56 ` Mike Fedyk
2001-11-29 3:13 ` Ken Brownfield
2001-11-29 3:30 ` Robert Love
2001-11-29 16:48 ` Marcelo Tosatti
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=20011129000509.A1362@markcomp.blaydon.hymers.org.uk \
--to=markh@linuxfromscratch.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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
all inboxes | Powered by JetHome®