From: Dave Jones <davej@redhat.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Hugh Dickins" <hugh@veritas.com>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
"Márcio Oliveira" <moliveira@latinsourcetech.com>,
linux-kernel@vger.kernel.org
Subject: Re: Tainted lsmod output
Date: Mon, 12 Sep 2005 21:21:46 -0400 [thread overview]
Message-ID: <20050913012146.GA15195@redhat.com> (raw)
In-Reply-To: <200509122016.j8CKGjmY029390@turing-police.cc.vt.edu>
On Mon, Sep 12, 2005 at 04:16:45PM -0400, Valdis.Kletnieks@vt.edu wrote:
> Somebody had an automated log-parsing tool, and wanted to make sure there
> were guaranteed at least 2 non-whitespace tokens on the line so they wouldn't
> have to deal with parsing 'Tainted: \n'?
That situation is impossible to hit. It'd be not tainted in that case.
The 'G' only gets shown if at least 1 other taint flag (typically 'M'
in my experience) is also set.
Dave
prev parent reply other threads:[~2005-09-13 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 18:21 Tainted lsmod output Márcio Oliveira
2005-09-12 18:30 ` Randy.Dunlap
2005-09-12 19:43 ` Hugh Dickins
2005-09-12 19:54 ` Randy.Dunlap
2005-09-12 19:58 ` Hugh Dickins
2005-09-12 20:03 ` Randy.Dunlap
2005-09-12 20:16 ` Valdis.Kletnieks
2005-09-12 21:27 ` Horst von Brand
2005-09-12 21:36 ` J. Bruce Fields
2005-09-13 1:21 ` Dave Jones [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=20050913012146.GA15195@redhat.com \
--to=davej@redhat.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moliveira@latinsourcetech.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