public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Piotrowski <michal.k.k.piotrowski@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Maciej Rutecki <maciej.rutecki@gmail.com>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Jarek Poplawski <jarkao2@o2.pl>,
	Mariusz Kozlowski <m.kozlowski@tuxland.pl>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: [ANNOUNCE] Linux Kernel Tester’s Guide v0.3-rc1
Date: Mon, 18 Jun 2007 22:11:51 +0200	[thread overview]
Message-ID: <4676E707.8020109@googlemail.com> (raw)

Hi,

We are pleased to announce the availability of "Linux Kernel Tester's Guide" v0.3-rc1.

This short guide describes the basics of kernel testing. The handbook is divided into six chapters:

1 The kernel, patches, trees and compilation
  1.1 The kernel
  1.2 Patches
  1.3 Ketchup
  1.4 Trees
  1.5 The -mm tree
  1.6 Compilation and installation
    1.6.1 Kernel compilation
    1.6.2 Useful make options
    1.6.3 Kernel modules
    1.6.4 Kernel hacking options
    1.6.5 Magic SysRq
    1.6.6 Installation
    1.6.7 Automated configuration and installation
2 Testing
  2.1 Phase One
  2.2 Phase Two (AutoTest)
  2.3 Phase Three
  2.4 Measuring performance
  2.5 Hello world! or What exactly are we looking for?
  2.6 Binary drivers and distribution kernels
3 Collecting kernel messages
  3.1 Syslog, console and dmesg
  3.2 Serial console
  3.3 Network console
4 Git, quilt and binary searching
  4.1  Git
  4.2  Quilt
  4.3  General idea of binary searching
  4.4  Binary searching with the help of quilt
  4.5  Binary searching with the help of git-bisect
  4.6  Caveats
5 Reporting bugs
6 Testing of hardware
A Related topics
  A.1 Test system
  A.2 KLive
  A.3 Sending patches
  A.4 How to become the kernel developer?
B License

PDF version
http://www.stardust.webpages.pl/files/handbook/handbook-en-0.3-rc1.pdf

LaTeX source
http://www.stardust.webpages.pl/files/handbook/handbook-current.tar.bz2

Any comments, suggestions and patches are welcome.

Huge thanks goes to Rafael J. Wysocki who translated the entire guide into English.
This is one of those rare cases when translation is better than original version :).

Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/

             reply	other threads:[~2007-06-18 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 20:11 Michal Piotrowski [this message]
2007-06-19 12:39 ` [ANNOUNCE] Linux Kernel Tester’s Guide v0.3-rc1 Clemens Koller
2007-06-19 16:16   ` Michal Piotrowski
2007-06-28 10:49     ` Clemens Koller
2007-06-21  6:50 ` Jan Engelhardt
2007-06-22  8:30   ` [ANNOUNCE] Linux Kernel Tester???s " Jarek Poplawski
2007-06-22 10:52     ` Jarek Poplawski
     [not found] ` <661de9470706210031s36396c31xff5428ff60042073@mail.gmail.com>
2007-06-21  8:30   ` [ANNOUNCE] Linux Kernel Tester’s " Michal Piotrowski
2007-06-21  8:43     ` Balbir Singh
2007-06-23 14:58 ` Rolf Eike Beer

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=4676E707.8020109@googlemail.com \
    --to=michal.k.k.piotrowski@gmail.com \
    --cc=bzolnier@gmail.com \
    --cc=jarkao2@o2.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.kozlowski@tuxland.pl \
    --cc=maciej.rutecki@gmail.com \
    --cc=randy.dunlap@oracle.com \
    --cc=rjw@sisk.pl \
    /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