From: Rob Landley <landley@trommello.org>
To: Andreas Dilger <adilger@turbolabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Tainted Modules Help Notices
Date: Wed, 10 Oct 2001 18:29:01 -0400 [thread overview]
Message-ID: <01101018290109.11498@localhost.localdomain> (raw)
In-Reply-To: <E15rQjC-0000m2-00@the-village.bc.nu> <m2itdnf6a9.fsf@anano.mitica> <20011010172832.P10443@turbolinux.com>
In-Reply-To: <20011010172832.P10443@turbolinux.com>
On Wednesday 10 October 2001 19:28, Andreas Dilger wrote:
> Given that "subversion" will only mean editing the text output of ksymoops
> to not display the "tainted" flag, I don't see it to be a big barrier to
> entry. If it is in the FAQ (or documented elsewhere) that "if ksymoops
> says 'tainted: 1' submit your bug reports only to the vendor" it will be
> a small matter to delete that line, and if this is NOT documented anywhere
> it will not reduce the number of bug submissions, which was the original
> goal.
If it gets them to read the FAQ, it's done it's job already!
What the flag REALLY means is "I didn't read the FAQ." In order to know to
change it, they have to know why it's there...
And it's not to reduce submissions, it's to let Kernel hackers discard them
more quickly. (No force on earth can stop clueless requests for tech
support. It's like trying to stop spam. All you can do is filter it more
effectively.)
Rob
next prev parent reply other threads:[~2001-10-11 2:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-10 8:06 Tainted Modules Help Notices Morgan Collins [Ax0n]
2001-10-10 8:20 ` David Woodhouse
2001-10-10 8:24 ` Morgan Collins [Ax0n]
2001-10-10 8:31 ` David Woodhouse
2001-10-10 13:50 ` Keith Owens
2001-10-10 13:59 ` Alexander Viro
2001-10-10 14:01 ` Keith Owens
2001-10-10 17:30 ` Alan Cox
2001-10-10 18:18 ` David Woodhouse
2001-10-10 20:06 ` Concerned Programmer
2001-10-10 20:28 ` Morgan Collins [Ax0n]
2001-10-10 21:28 ` Keith Owens
2001-10-10 22:03 ` Anthony DeRobertis
2001-10-11 7:27 ` David Woodhouse
2001-10-10 21:17 ` Alan Cox
2001-10-10 23:02 ` Juan Quintela
2001-10-10 23:28 ` Andreas Dilger
2001-10-10 22:29 ` Rob Landley [this message]
2001-10-11 2:48 ` 2.4.11 UDF Morgan Collins [Ax0n]
2001-10-11 3:26 ` Craig Whitmore
2001-10-11 8:50 ` Tainted Modules Help Notices Andreas Ferber
2001-10-11 9:25 ` Alan Cox
2001-10-11 9:35 ` Henning P. Schmiedehausen
2001-10-11 9:41 ` Pekka Pietikäinen
2001-10-11 9:48 ` Syed Mohammad Talha
2001-10-11 10:09 ` Concerned Programmer
2001-10-11 10:37 ` Alan Cox
2001-10-11 22:42 ` David Schwartz
2001-10-11 23:40 ` John Alvord
2001-10-12 1:12 ` David Schwartz
2001-10-12 1:32 ` Robert Love
2001-10-11 12:10 ` James Sutherland
2001-10-10 14:13 ` David Woodhouse
2001-10-10 14:18 ` Alexander Viro
2001-10-10 13:10 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 14:06 Bonds, Deanna
2001-10-10 14:24 ` Arjan van de Ven
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=01101018290109.11498@localhost.localdomain \
--to=landley@trommello.org \
--cc=adilger@turbolabs.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