public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, jenglish@flightlab.com
Subject: Re: MODULE_LICENSE string for LGPL drivers?
Date: Tue, 16 Apr 2002 20:33:17 +0200	[thread overview]
Message-ID: <28D84983F86@vcnet.vc.cvut.cz> (raw)

On 16 Apr 02 at 19:31, Alan Cox wrote:
> > What should I use for the MODULE_LICENSE() string in a driver
> > that is distributed under the LGPL?  "LGPL" isn't listed in
> > include/linux/module.h as an "untainted" license, so should I
> 
> When LGPL code is linked with GPL code then the result becomes GPL. So
> once you have the code combined with the kernel it is GPL unless its
> a seperate work.

I do not want to be flammed, but source file itself is still LGPLed,
so stating "GPL" in source is at least misleading to users who will use 
same source under NT kernel. I think that modutils (if anyone) should know 
this metamorphose.

And license on the file itself definitely does not change by compilation,
as this would for example change glibc licensing to GPL just by anyone
linking his GPLed application statically with glibc.
                                                    Best regards,
                                                        Petr Vandrovec
                                                        vandrove@vc.cvut.cz
                                                        

             reply	other threads:[~2002-04-16 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 18:33 Petr Vandrovec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-16 18:00 MODULE_LICENSE string for LGPL drivers? Joe English
2002-04-16 18:31 ` Alan Cox

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=28D84983F86@vcnet.vc.cvut.cz \
    --to=vandrove@vc.cvut.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jenglish@flightlab.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