public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe English <jenglish@flightlab.com>
To: linux-kernel@vger.kernel.org
Subject: MODULE_LICENSE string for LGPL drivers?
Date: Tue, 16 Apr 2002 11:00:06 -0700	[thread overview]
Message-ID: <200204161800.g3GI06f22193@dragon.flightlab.com> (raw)


Hello all,

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
use "GPL and additional rights" instead?

I don't *think* I'm running into problems with EXPORT_SYMBOL_GPL --
the driver has been working fine under 2.4 kernels
and I only recently found out about MODULE_LICENSE and
*that* whole mess -- but am not sure, since I've also
got an older version of modutils which probably isn't
performing the taint check.

Unfortunately switching to the GPL is not an option;
the driver was written for a third party and must be
distributed with firmware (proprietary, binary-only)
and client libraries (source available but still proprietary)
over whose license terms I have no control.

Alternately, I could just let it taint the kernel.


Thanks for any advice.  Cc:'s to jenglish@flightlab.com
will be appreciated; I am not subscribed to this list, but
will try to keep up via the web archives.


--Joe English

  jenglish@flightlab.com

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

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

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=200204161800.g3GI06f22193@dragon.flightlab.com \
    --to=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