From: "Brian F. G. Bidulock" <bidulock@openss7.org>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
devmazumdar <dev@opensound.com>,
linux-kernel@vger.kernel.org
Subject: Re: How to check if kernel sources are installed on a system?
Date: Sun, 28 May 2006 22:44:02 -0600 [thread overview]
Message-ID: <20060528224402.A13279@openss7.org> (raw)
In-Reply-To: <1148846131.27461.14.camel@mindpipe>; from rlrevell@joe-job.com on Sun, May 28, 2006 at 03:55:29PM -0400
Lee,
On Sun, 28 May 2006, Lee Revell wrote:
>
> Debugging. When a new Linux user files a "no sound" ALSA bug report I
> need to find out whether they have any known broken options enabled,
> like USB bandwidth checking or the OSS USB midi/audio drivers. If we
> have to go back and forth figuring out which distro they have and where
> the config is they are that much more likely to give up and go back to
> Windows.
>
Bug reports is another advantage that I found with the autoconf
approach to building kernel modules (previous cited): automatic
generation of bug reports containing full configuration information
using a send-pr script generated by the 'configure' script.
--brian
next prev parent reply other threads:[~2006-05-29 4:44 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 21:19 How to check if kernel sources are installed on a system? devmazumdar
2006-05-25 21:27 ` alan
2006-05-25 21:29 ` Jan-Benedict Glaw
2006-05-25 22:02 ` Lee Revell
2006-05-25 22:15 ` 4Front Technologies
2006-05-25 22:25 ` Lee Revell
2006-05-25 22:34 ` Dave Jones
2006-05-25 22:40 ` Lee Revell
2006-05-25 21:29 ` Valdis.Kletnieks
2006-05-25 21:35 ` Dave Jones
2006-05-25 21:32 ` Michal Piotrowski
2006-05-25 21:34 ` Jeff Garzik
2006-05-25 21:39 ` Jan-Benedict Glaw
2006-05-25 21:42 ` Jeff Garzik
2006-05-26 14:36 ` Jan-Benedict Glaw
2006-05-25 21:44 ` Dave Jones
2006-05-25 22:52 ` Olivier Galibert
2006-05-26 4:23 ` Willy Tarreau
2006-05-26 14:37 ` Jan-Benedict Glaw
2006-05-26 15:01 ` linux-os (Dick Johnson)
2006-05-27 10:47 ` Jesper Juhl
2006-05-25 21:41 ` Dave Jones
2006-05-25 22:29 ` Lee Revell
2006-05-25 22:39 ` 4Front Technologies
2006-05-25 23:06 ` Jesper Juhl
2006-05-25 23:16 ` 4Front Technologies
2006-05-26 0:12 ` Brian F. G. Bidulock
2006-05-25 23:00 ` Diego Calleja
2006-05-26 0:24 ` Måns Rullgård
2006-05-26 14:29 ` Arjan van de Ven
2006-05-26 15:35 ` Brian F. G. Bidulock
2006-05-27 12:21 ` Arjan van de Ven
2006-05-27 19:52 ` Brian F. G. Bidulock
2006-05-27 20:21 ` Arjan van de Ven
2006-05-27 22:21 ` Brian F. G. Bidulock
2006-05-28 8:27 ` Arjan van de Ven
2006-05-28 10:13 ` Brian F. G. Bidulock
2006-05-27 14:41 ` Kyle Moffett
2006-05-27 22:05 ` Brian F. G. Bidulock
2006-05-28 13:03 ` Heiko Carstens
2006-05-28 13:12 ` Jan-Benedict Glaw
2006-05-28 13:45 ` Heiko Carstens
2006-05-28 17:03 ` Arjan van de Ven
2006-05-28 17:52 ` Lee Revell
2006-05-28 18:12 ` Arjan van de Ven
2006-05-28 18:22 ` Randy.Dunlap
2006-05-28 19:10 ` Willy Tarreau
2006-05-28 19:55 ` Lee Revell
2006-05-28 20:45 ` Jan-Benedict Glaw
2006-05-28 21:27 ` Lee Revell
2006-05-28 21:55 ` Jan-Benedict Glaw
2006-05-28 22:02 ` Lee Revell
2006-05-28 22:38 ` Jan-Benedict Glaw
2006-05-29 12:11 ` Steven Rostedt
2006-05-29 12:38 ` Steven Rostedt
2006-05-29 4:44 ` Brian F. G. Bidulock [this message]
2006-05-29 4:52 ` Arjan van de Ven
2006-05-29 5:35 ` 4Front Technologies
2006-05-29 5:46 ` David Miller
2006-05-29 5:59 ` Valdis.Kletnieks
2006-05-29 6:09 ` Willy Tarreau
2006-05-29 6:11 ` Arjan van de Ven
2006-05-29 6:57 ` Brian F. G. Bidulock
2006-05-29 7:01 ` Arjan van de Ven
2006-05-29 7:29 ` Brian F. G. Bidulock
2006-05-29 7:05 ` 4Front Technologies
2006-05-29 7:23 ` Brian F. G. Bidulock
2006-05-29 7:43 ` Valdis.Kletnieks
2006-05-29 12:23 ` Arjan van de Ven
2006-05-29 15:52 ` Christopher Friesen
2006-05-29 16:00 ` Arjan van de Ven
2006-05-28 20:40 ` Jesper Juhl
2006-05-25 22:51 ` Jesper Juhl
2006-05-26 0:09 ` Thomas Backlund
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=20060528224402.A13279@openss7.org \
--to=bidulock@openss7.org \
--cc=arjan@infradead.org \
--cc=dev@opensound.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox