From: Carsten Otte <cotte@freenet.de>
To: li nux <lnxluv@yahoo.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: 2.6: problem with module tainting the kernel
Date: Sat, 11 Jun 2005 23:42:03 +0200 [thread overview]
Message-ID: <42AB5AAB.2030303@freenet.de> (raw)
In-Reply-To: <20050610152450.82261.qmail@web33315.mail.mud.yahoo.com>
li nux wrote:
>In 2.6 kernels how to assure that on inserting our own
>module, it doesn't throw the warning:
>
>"unsupported module, tainting kernel"
>
>what tainting depends on apart from the license string ?
>
>
Guess you're using a SuSE Kernel? That one gets tainted once you
load a module that SuSE does not support (meaning, you cannot call
them and complain about the module). No technical problem.
cheers,
Carsten
prev parent reply other threads:[~2005-06-11 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 15:24 2.6: problem with module tainting the kernel li nux
2005-06-10 15:35 ` Christoph Hellwig
2005-06-11 3:11 ` randy_dunlap
2005-06-11 3:18 ` randy_dunlap
2005-06-12 9:25 ` li nux
2005-06-12 15:31 ` Carlos Martin
2005-06-11 21:42 ` Carsten Otte [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=42AB5AAB.2030303@freenet.de \
--to=cotte@freenet.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lnxluv@yahoo.com \
/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