aboutsummaryrefslogtreecommitdiffstats
path: root/HOWTO
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@suse.de>2005-11-15 12:58:57 -0800
committerGreg Kroah-Hartman <gregkh@suse.de>2005-11-15 12:58:57 -0800
commitb05c646f8777ab73c755f71f57a10ec6b9046021 (patch)
treef98f56fee7329a9f894b0bcc379afaefcafddb3e /HOWTO
parentb1fa5df46e2bd7106c31f891d0eaa8ab7e3b1d8c (diff)
downloadpatches-b05c646f8777ab73c755f71f57a10ec6b9046021.tar.gz
add LXR section
Diffstat (limited to 'HOWTO')
-rw-r--r--HOWTO24
1 files changed, 17 insertions, 7 deletions
diff --git a/HOWTO b/HOWTO
index d3c14b9a5a657..2e7f017e48d4e 100644
--- a/HOWTO
+++ b/HOWTO
@@ -161,8 +161,9 @@ real-time, and a lot of helpful documentation that is useful for
learning about Linux kernel development.
The website has basic information about code organization, subsystems,
-and current projects (both in-tree and out-of-tree). It also describes some
-basic logistical information, like how to compile a kernel and apply a patch.
+and current projects (both in-tree and out-of-tree). It also describes
+some basic logistical information, like how to compile a kernel and
+apply a patch.
If you do not know where you want to start, but you want to look for
some task to start doing to join into the kernel development community,
@@ -175,13 +176,22 @@ will learn the basics of getting your patch into the Linux kernel tree,
and possibly be pointed in the direction of what to go work on next, if
you do not already have an idea.
-
-If you already have a chunk of code that you want to put into the
-kernel tree, but need some help getting it in the proper form, the
+If you already have a chunk of code that you want to put into the kernel
+tree, but need some help getting it in the proper form, the
kernel-mentors project was created to help you out with this. It is a
mailing list, and can be found at:
http://selenic.com/mailman/listinfo/kernel-mentors
+Before making any actual modifications to the Linux kernel code, it is
+imperative to understand how the code in question works. For this
+purpose, nothing is better than reading through it directly (most tricky
+bits are commented well), perhaps even with the help of specialized
+tools. One such tool that is particularly recommended is the Linux
+Cross-Reference project, which is able to present source code in a
+self-referential, indexed webpage format. An excellent up-to-date
+repository of the kernel code may be found at:
+ http://sosdg.org/~coywolf/lxr/
+
The development process
-----------------------
@@ -574,8 +584,8 @@ to be based on text he had written, and to Randy Dunlap and Gerrit
Huizenga for some of the list of things you should and should not say.
Also thanks to Pat Mochel, Hanna Linder, Randy Dunlap, Kay Sievers,
Vojtech Pavlik, Jan Kara, Josh Boyer, Kees Cook, Andrew Morton, Andi
-Kleen, and Alex Shepard for their review and comments on early drafts of
-this document.
+Kleen, Vadim Lobanov, and Alex Shepard for their review and comments on
+early drafts of this document.