From: Nick Bowler <nbowler@elliptictech.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH trivial] docs: Describe the 'C' taint flag in oops-tracing.txt.
Date: Tue, 6 Oct 2009 10:12:22 -0400 [thread overview]
Message-ID: <20091006141222.GA18579@emergent.ellipticsemi.com> (raw)
From: Nick Bowler <nbowler@elliptictech.com>
If some of the flags are documented there, they all should be.
Signed-off-by: Nick Bowler <nbowler@elliptictech.com>
---
Documentation/oops-tracing.txt | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/Documentation/oops-tracing.txt b/Documentation/oops-tracing.txt
index b152e81..c10c022 100644
--- a/Documentation/oops-tracing.txt
+++ b/Documentation/oops-tracing.txt
@@ -257,6 +257,8 @@ characters, each representing a particular tainted value.
10: 'W' if a warning has previously been issued by the kernel.
+ 11: 'C' if a staging driver has been loaded.
+
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
--
1.6.4.4
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next reply other threads:[~2009-10-06 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 14:12 Nick Bowler [this message]
2009-10-06 17:29 ` [PATCH trivial] docs: Describe the 'C' taint flag in oops-tracing.txt Randy Dunlap
2009-10-06 17:53 ` Jiri Kosina
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=20091006141222.GA18579@emergent.ellipticsemi.com \
--to=nbowler@elliptictech.com \
--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