Messages in this thread | | | Date | Tue, 6 Oct 2009 10:29:57 -0700 | From | Randy Dunlap <> | Subject | Re: [PATCH trivial] docs: Describe the 'C' taint flag in oops-tracing.txt. |
| |
On Tue, 6 Oct 2009 10:12:22 -0400 Nick Bowler wrote:
> 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>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
> --- > 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 > --
--- ~Randy
| |