From: Scott Robert Ladd <coyote@coyotegulch.com>
To: linux-kernel@vger.kernel.org
Subject: Testing: What do you want?
Date: Mon, 24 Mar 2003 09:46:05 -0500 [thread overview]
Message-ID: <3E7F1A2D.4050306@coyotegulch.com> (raw)
OSNews and LinuxJournal are urging people to test the Linux kernel. I've
been doing so for several months now, running the latest kernel live on
my primary development system. I figure the best way to know if the
kernel works is to use it when I'm working. ;)
At the moment, my biggest contribution to kernel development is testing,
given that I'm not yet comfortable hacking kernel code in public. My
question is: What do the kernel developers want from testers? What sort
of reports are helpful? Is there anything in particular that needs
extensive testing?
I haven't found a "Guide to Testing the Kernel" anywhere -- perhaps such
a document exists, but I've missed it. Such a document could provide
basic information for "testing newbies."
My experience thus far:
For the most part, the 2.5 series has worked very well for me, albeit
with a few glitches (radeonfb, for example, as reported last week.) I'll
build the 2.5.65 kernel on my Sparc later today, and see how well it
works there.
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.
next reply other threads:[~2003-03-24 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-24 14:46 Scott Robert Ladd [this message]
2003-03-24 15:39 ` Testing: What do you want? Jan-Benedict Glaw
2003-03-24 17:30 ` Scott Robert Ladd
2003-03-25 0:04 ` Rob Radez
2003-03-25 17:50 ` Craig Thomas
2003-03-24 17:01 ` Alan Cox
2003-03-24 23:06 ` Craig Thomas
2003-03-25 0:16 ` Jörn Engel
2003-03-25 14:18 ` Scott Robert Ladd
2003-03-25 14:18 ` Scott Robert Ladd
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=3E7F1A2D.4050306@coyotegulch.com \
--to=coyote@coyotegulch.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 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.