From: "Manfred Spraul" <manfred@colorfullife.com>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>,
"Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: <lm@bitmover.com>, <linux-kernel@vger.kernel.org>
Subject: Re: bug database braindump from the kernel summit
Date: Sun, 1 Apr 2001 23:48:56 +0200 [thread overview]
Message-ID: <004601c0baf5$8fac4700$5517fea9@local> (raw)
In-Reply-To: <Pine.LNX.3.96.1010401160430.28121K-100000@mandrakesoft.mandrakesoft.com>
From: "Jeff Garzik" <jgarzik@mandrakesoft.com>
>
> /proc/pci data alone with every bug report is usually invaluable.
Even if the bug is a compile error?
E.g.
BUG REPORT (a real one, I didn't have the time yet to post a patch):
kernel versions: tested with 2.4.2-ac24, afaics 2.4.3 is also affected
Description:
Several config options are missing in the 'if' at the end of
linux/drivers/net/pcmcia/Config.in.
This means that CONFIG_PCMCIA_NETCARD is not set, and then (iirc) the
kernel won't link.
CONFIG_ARCNET_COM20020_CS
CONFIG_PCMCIA_HERMES
CONFIG_AIRONET4500_CS
CONFIG_PCMCIA_IBMTR
are missing.
Obviously too much data doesn't hurt, as long as
* it's hidden somewhere deep in a database, clearly separated from the
important parts (if there is an oops: decoded oops, description, how
easy is it to trigger the bug, steps to reproduce)
* very easy for the bug reporter to collect.
* not mandatory.
--
Manfred
next prev parent reply other threads:[~2001-04-01 21:49 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-01 19:32 bug database braindump from the kernel summit Manfred Spraul
2001-04-01 20:17 ` Albert D. Cahalan
2001-04-01 21:07 ` Jeff Garzik
2001-04-01 21:48 ` Manfred Spraul [this message]
2001-04-01 22:48 ` Jeff Garzik
2001-04-01 23:01 ` David Lang
2001-04-01 23:21 ` Jeff Garzik
2001-04-01 23:25 ` David Lang
2001-04-01 23:34 ` Jeff Garzik
2001-04-01 23:32 ` David Lang
2001-04-01 23:44 ` Jeff Garzik
2001-04-01 23:43 ` David Lang
2001-04-02 0:26 ` Ben Ford
2001-04-02 18:57 ` Kai Henningsen
2001-04-05 12:55 ` Petr Baudis
2001-04-02 5:26 ` Richard Russon
2001-04-02 21:35 ` Steven Walter
2001-04-02 19:39 ` Oliver Xymoron
2001-04-02 21:40 ` J . A . Magallon
2001-04-02 22:09 ` Jeff Garzik
2001-04-02 22:24 ` David Lang
2001-04-02 22:38 ` J . A . Magallon
2001-04-02 23:04 ` Tom Leete
2001-04-02 23:12 ` Oliver Xymoron
2001-04-02 23:24 ` Jeff Garzik
2001-04-02 23:31 ` Oliver Xymoron
2001-04-03 16:05 ` Miles Lane
2001-04-02 1:49 ` Miles Lane
2001-04-01 20:59 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2001-04-01 22:34 Stephen Satchell
2001-04-02 8:00 ` Olaf Titz
2001-04-01 17:54 Larry McVoy
2001-04-01 19:43 ` Albert D. Cahalan
2001-04-01 20:21 ` Gregory Maxwell
2001-04-01 20:38 ` Albert D. Cahalan
2001-04-01 21:16 ` David Lang
2001-04-01 21:18 ` David Lang
2001-04-02 1:57 ` Miles Lane
2001-04-02 5:07 ` David Lang
2001-04-01 23:14 ` Jeff Garzik
2001-04-02 13:31 ` Rogier Wolff
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='004601c0baf5$8fac4700$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=acahalan@cs.uml.edu \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.