linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: mtk.manpages@gmail.com, linux-kernel@vger.kernel.org,
	linux-api@vger.kernel.org
Subject: Re: [PATCH] Document kernel taint flags properly
Date: Mon, 20 Oct 2008 14:40:18 -0700	[thread overview]
Message-ID: <20081020214018.GA28903@kroah.com> (raw)
In-Reply-To: <48FCFA30.9000707@xenotime.net>

On Mon, Oct 20, 2008 at 02:37:52PM -0700, Randy Dunlap wrote:
> Greg KH wrote:
> > On Sat, Oct 18, 2008 at 03:51:11AM -0500, Michael Kerrisk wrote:
> >   
> >> Greg,
> >>
> >> Small corrections below.
> >>
> >> On Fri, Oct 17, 2008 at 5:55 PM, Greg KH <greg@kroah.com> wrote:
> >>     
> >>> From: Greg Kroah-Hartman <gregkh@suse.de>
> >>>
> >>> This fills in the documentation for all of the current kernel taint
> >>> flags, and fixes the number for TAINT_CRAP, which was incorrectly
> >>> described.
> >>>
> >>> Cc: Michael Kerrisk <mtk.manpages@gmail.com>
> >>> Cc: Randy Dunlap <rdunlap@xenotime.net>
> >>> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> >>>
> >>> ---
> >>>  Documentation/sysctl/kernel.txt |   24 +++++++++++++++++-------
> >>>  1 file changed, 17 insertions(+), 7 deletions(-)
> >>>
> >>> --- a/Documentation/sysctl/kernel.txt
> >>> +++ b/Documentation/sysctl/kernel.txt
> >>> @@ -363,11 +363,21 @@ tainted:
> >>>  Non-zero if the kernel has been tainted.  Numeric values, which
> >>>  can be ORed together:
> >>>
> >>> -  1 - A module with a non-GPL license has been loaded, this
> >>> -      includes modules with no license.
> >>> -      Set by modutils >= 2.4.9 and module-init-tools.
> >>> -  2 - A module was force loaded by insmod -f.
> >>> -      Set by modutils >= 2.4.9 and module-init-tools.
> >>> -  4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
> >>> - 64 - A module from drivers/staging was loaded.
> >>> +   1 - A module with a non-GPL license has been loaded, this
> >>> +       includes modules with no license.
> >>> +       Set by modutils >= 2.4.9 and module-init-tools.
> >>> +   2 - A module was force loaded by insmod -f.
> >>> +       Set by modutils >= 2.4.9 and module-init-tools.
> >>> +   4 - Unsafe SMP processors: SMP with CPUs not designed for SMP.
> >>> +   8 - A module was forcefully unloaded from the system by rmmod -f.
> >>>       
> >> s/forcefully/forcibly/
> >>
> >>     
> >>> +  16 - A hardware machine check error occured on the system.
> >>>       
> >> occurred
> >>     
> >
> > Thanks, I've updated this in my version.
> >
> > Randy, I can send this through my tree, is that ok?  Or do you want it
> > to go through yours?
> >   
> You please go ahead with it.

Will do.

thanks,

greg k-h

      reply	other threads:[~2008-10-20 21:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17 22:55 [PATCH] Document kernel taint flags properly Greg KH
     [not found] ` <20081017225515.GA14133-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2008-10-18  8:51   ` Michael Kerrisk
     [not found]     ` <cfd18e0f0810180151v232f623pdbf0f12cad6532d6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-10-20 20:43       ` Greg KH
2008-10-20 21:37         ` Randy Dunlap
2008-10-20 21:40           ` Greg KH [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=20081020214018.GA28903@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=rdunlap@xenotime.net \
    /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;
as well as URLs for NNTP newsgroup(s).