public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Jon Masters <jonathan@jonmasters.org>
Cc: linux-kernel@vger.kernel.org, jcm@jonmasters.org
Subject: Re: [PATCH] add module taint on ndiswrapper
Date: Tue, 22 Jan 2008 10:21:12 +1100	[thread overview]
Message-ID: <200801221021.12984.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080121204341.GA29679@dallas.jonmasters.org>

On Tuesday 22 January 2008 07:43:41 Jon Masters wrote:
> The struct module taints member is supposed to store per-module taint
> data. The kernel knows about certain specific external modules that will
> taint the kernel, such as ndiswrapper. Use of ndiswrapper possibly
> should set the per-module taint in addition to the global kernel
> taint flag, unless we're arguing not because wrapper module itself
> is not what actually causes the kernel to be tainted as such?
>
> Signed-off-by: Jon Masters <jcm@jonmasters.org>

Thanks, applied.

Rusty.

      reply	other threads:[~2008-01-21 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 20:43 [PATCH] add module taint on ndiswrapper Jon Masters
2008-01-21 23:21 ` Rusty Russell [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=200801221021.12984.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=jcm@jonmasters.org \
    --cc=jonathan@jonmasters.org \
    --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