From: "Daniel Bonekeeper" <thehazard@gmail.com>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Valdis.Kletnieks@vt.edu" <Valdis.Kletnieks@vt.edu>,
"Adrian Bunk" <bunk@stusta.de>,
linux-kernel@vger.kernel.org
Subject: Re: Automatic Kernel Bug Report
Date: Mon, 10 Jul 2006 12:40:07 -0500 [thread overview]
Message-ID: <e1e1d5f40607101040u3baf0da7r43d5538700b02e2@mail.gmail.com> (raw)
In-Reply-To: <20060710081131.GA2251@elf.ucw.cz>
On 7/10/06, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
Hi ! =)
>
> Well, unless we have some volunteer to go through the bugreports and
> sort them/kill the invalid ones/etc... this is going to do more harm
> than good.
As I told before, I wouldn't care to do that, as long as I know that
it is actually being used (and useful). The system (at the server
side) could automatically route some reports (mark them as "tainted
modules detected", etc, that sort of mechanical stuff), and according
to the frequency of certain bugs, I could check if they are actually
real bugs. If so, they get reported here on LKML. Since we can expect,
maybe, dozens of thousands of reports per week, wouldn't be hard to
distinct between real bugs, etc (if we use frequency as a marker). For
example, if the number of reports on Suspend2 get risen up sensitively
on some just-released kernel, this means that something that was added
isn't working (so here comes the personal debug, where we can see if
it's a new bug or a regression)
Daniel
--
What this world needs is a good five-dollar plasma weapon.
next prev parent reply other threads:[~2006-07-10 17:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-09 8:45 Daniel Bonekeeper
2006-07-09 9:45 ` Michal Piotrowski
2006-07-09 10:29 ` Daniel Bonekeeper
2006-07-09 12:58 ` Adrian Bunk
2006-07-09 18:46 ` Daniel Bonekeeper
2006-07-09 19:11 ` Adrian Bunk
2006-07-09 20:01 ` Daniel Bonekeeper
2006-07-09 20:19 ` Valdis.Kletnieks
2006-07-09 20:27 ` Daniel Bonekeeper
2006-07-10 8:11 ` Pavel Machek
2006-07-10 17:40 ` Daniel Bonekeeper [this message]
2006-07-10 17:59 ` Valdis.Kletnieks
2006-07-10 22:05 ` Daniel Bonekeeper
2006-07-10 23:41 ` Lee Revell
2006-07-11 1:15 ` Daniel Bonekeeper
2006-07-10 18:41 ` Horst von Brand
2006-07-10 21:34 ` Daniel Bonekeeper
2006-07-11 14:16 ` Horst von Brand
2006-07-09 20:24 ` Diego Calleja
2006-07-09 20:37 ` Daniel Bonekeeper
2006-07-09 22:19 ` Diego Calleja
2006-07-09 22:49 ` Daniel Bonekeeper
2006-07-09 20:25 ` Jesper Juhl
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=e1e1d5f40607101040u3baf0da7r43d5538700b02e2@mail.gmail.com \
--to=thehazard@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bunk@stusta.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®