All of lore.kernel.org
 help / color / mirror / Atom feed
From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: randy.dunlap@oracle.com, tytso@mit.edu
Subject: + update-doc-oops-tracingtxt-for-taint_user-fix.patch added to -mm tree
Date: Fri, 16 Feb 2007 13:24:01 -0800	[thread overview]
Message-ID: <200702162124.l1GLO1nq010230@shell0.pdx.osdl.net> (raw)


The patch titled
     update Doc/oops-tracing.txt for TAINT_USER (fix)
has been added to the -mm tree.  Its filename is
     update-doc-oops-tracingtxt-for-taint_user-fix.patch

*** Remember to use Documentation/SubmitChecklist when testing your code ***

See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this

------------------------------------------------------
Subject: update Doc/oops-tracing.txt for TAINT_USER (fix)
From: Randy Dunlap <randy.dunlap@oracle.com>

Add TAINT_USER description to Tainted flags in oops-tracing.txt.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 Documentation/oops-tracing.txt |    3 +++
 1 files changed, 3 insertions(+)

diff -puN Documentation/oops-tracing.txt~update-doc-oops-tracingtxt-for-taint_user-fix Documentation/oops-tracing.txt
--- a/Documentation/oops-tracing.txt~update-doc-oops-tracingtxt-for-taint_user-fix
+++ a/Documentation/oops-tracing.txt
@@ -237,6 +237,9 @@ characters, each representing a particul
   7: 'U' if a user specifically requested that the Tainted flag be set,
      ' ' otherwise.
 
+  7: 'U' if a user or user application specifically requested that the
+     Tainted flag be set, ' ' otherwise.
+
 The primary reason for the 'Tainted: ' string is to tell kernel
 debuggers if this is a clean kernel or if anything unusual has
 occurred.  Tainting is permanent: even if an offending module is
_

Patches currently in -mm which might be from randy.dunlap@oracle.com are

origin.patch
irq-kernel-doc-fixes.patch
git-acpi.patch
build-errors-uevent-with-config_sysfs=n.patch
sata-use-null-for-ptrs.patch
git-mtd.patch
git-netdev-all.patch
phy-layer-add-kernel-doc-docbook.patch
parisc-fix-module_param-iommu-permission.patch
ueagle-atmc-needs-schedh.patch
kernel-doc-include-struct-short-description-in-title.patch
tty-use-null-for-ptrs.patch
cdrom-use-unsigned-bitfields.patch
update-doc-oops-tracingtxt-for-taint_user.patch
update-doc-oops-tracingtxt-for-taint_user-fix.patch
extend-notifier_call_chain-to-count-nr_calls-made-fixes.patch
reiser4-use-null-for-pointers.patch
profile_likely-export-do_check_likely.patch

                 reply	other threads:[~2007-02-16 21:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200702162124.l1GLO1nq010230@shell0.pdx.osdl.net \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=tytso@mit.edu \
    /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.