public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: li nux <lnxluv@yahoo.com>
Cc: linux <linux-kernel@vger.kernel.org>
Subject: Re: 2.6: problem with module tainting the kernel
Date: Fri, 10 Jun 2005 16:35:06 +0100	[thread overview]
Message-ID: <20050610153506.GA8118@infradead.org> (raw)
In-Reply-To: <20050610152450.82261.qmail@web33315.mail.mud.yahoo.com>

On Fri, Jun 10, 2005 at 08:24:50AM -0700, 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"

There's no place in the kernel that produces this message.  Are you
using some odd vendor tree?


  reply	other threads:[~2005-06-10 15:41 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 [this message]
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

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=20050610153506.GA8118@infradead.org \
    --to=hch@infradead.org \
    --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