All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Smith <steven@serisilks.screaming.net>
To: David Stroupe <dstroupe@keyed-upsoftware.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Error message when insmodding
Date: Wed, 17 Apr 2002 20:22:18 +0100	[thread overview]
Message-ID: <20020417192218.GA309@archibold> (raw)
In-Reply-To: <3CBD9CDC.2070202@keyed-upsoftware.com>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

> Warning:  loading driver.o will taint the kernel : no license
> 
> This is a driver that I created myself and it seems to load and function 
> properly regardless of this message.
> 
> What does this mean?
Recent kernels have a ``MODULE_LICENSE'' macro, which allows you to specify
a license for your module. This is so as kernels with binary-only modules
are flagged as such in bug reports, and don't cause people to waste too much
time with unfixable problems. All this warning means is that your module
has no MODULE_LICENSE.

The tainted bit just means that something odd has happened which will make
bug reports less useful/accurate.

> How do I resolve it?
Add a MODULE_LICENSE. This is defined in linux/module.h, and is used as:

MODULE_LICENSE("Name of your license");

somewhere near the bottom of your module. Licenses recognised by insmod
are (without checking):

GPL
Dual MPL/GPL
Dual BSD/GPL
GPL and additional rights

Anything else will probably get rid of your error message, but won't let
you use GPLONLY kernel exports.

Steven Smith,
sos22@cam.ac.uk.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

      reply	other threads:[~2002-04-17 19:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-17 16:03 Error message when insmodding David Stroupe
2002-04-17 19:22 ` Steven Smith [this message]

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=20020417192218.GA309@archibold \
    --to=steven@serisilks.screaming.net \
    --cc=dstroupe@keyed-upsoftware.com \
    --cc=linux-newbie@vger.kernel.org \
    --cc=sos22@cam.ac.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.