public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [RFC] HOWTO do Linux kernel development - take 2
Date: Tue, 15 Nov 2005 21:47:24 -0800	[thread overview]
Message-ID: <20051116054724.GA30413@kroah.com> (raw)
In-Reply-To: <20051116021754.GM5735@stusta.de>

On Wed, Nov 16, 2005 at 03:17:54AM +0100, Adrian Bunk wrote:
> On Tue, Nov 15, 2005 at 05:10:32PM -0800, Greg KH wrote:
> > On Wed, Nov 16, 2005 at 01:23:48AM +0100, Adrian Bunk wrote:
> >...
> > > LDD (as you might have heard, it's also available online for free ;-) )
> > > and the book by Robert Love are good starting points for learning kernel 
> > > programming, and they should IMHO be listed here.
> > 
> > But that's what the Documentation/kernel-docs.txt file has in it.  I
> 
> It seems you haven't looked at kernel-docs.txt before saying this...
> 
> kernel-docs.txt is so heavily outdated we should better remove it.

No, we should clean it up and update it.  I think that Randy is
currently working on this.

> > don't want to get into judging which kernel books go into this file, as
> > people might think I am a bit biased :)
> 
> Judging from the questions I see from newbies on linux-kernel (who 
> should be the target audience of your document), you are omitting the 
> answer to the most frequently asked question.
> 
> I'd say noone disagrees that LDD and the book by Robert Love are the 
> books mentioned most often (and by different kernel developers) when 
> people ask which book to read as introduction for kernel hacking.

This document is to help describe the non-technical things about Linux
kernel development.  The things that are not doucumented well, the
process and procedures that we go through to create this kernel.

The technical things are covered very well, by lots of other documents,
magazines, sites, and books.  We should list those in the
kernel-docs.txt file.

> > > > Becoming A Kernel Developer
> > > > ---------------------------
> > > >...
> > > > 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
> > > 
> > > 
> > > This list seems to be nearly dead, and it seems the following one is now 
> > > used instead:
> > >    http://mail.nl.linux.org/kernelnewbies/
> > 
> > I do mention the kernelnewbies project, which includes the mailing list.
> > I hope the mentor's project picks up, I just think not enough people
> > realize it is there.
> >...
> 
> It's perhaps a bit out of the scope of this discussion, but do we really 
> need both of these lists? I don't see any real difference between them.

It is out of the scope of this discussion :)

thanks,

greg k-h

  reply	other threads:[~2005-11-16  6:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-15 21:05 [RFC] HOWTO do Linux kernel development - take 2 Greg KH
2005-11-15 21:52 ` Avuton Olrich
2005-11-15 21:54   ` Greg KH
2005-11-16  5:31   ` Rogério Brito
2005-11-16  5:38     ` Greg KH
2005-11-15 22:06 ` Jesper Juhl
2005-11-15 22:01   ` Greg KH
2005-11-15 22:08 ` Andreas Schwab
2005-11-15 21:59   ` Greg KH
2005-11-15 22:21 ` Jesper Juhl
2005-11-15 22:30   ` Greg KH
2005-11-18  5:40     ` Jody McIntyre
2005-11-21 22:03       ` Greg KH
2005-11-15 22:27 ` Jesper Juhl
2005-11-15 22:36   ` Greg KH
2005-11-16  0:23 ` Adrian Bunk
2005-11-16  1:10   ` Greg KH
2005-11-16  1:46     ` Coywolf Qi Hunt
2005-11-16  2:01       ` Alistair John Strachan
2005-11-16  2:17     ` Adrian Bunk
2005-11-16  5:47       ` Greg KH [this message]
2005-11-16 17:28 ` David Woodhouse
2005-11-16 17:38   ` Randy.Dunlap
2005-11-16 17:40   ` Jörn Engel

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=20051116054724.GA30413@kroah.com \
    --to=greg@kroah.com \
    --cc=bunk@stusta.de \
    --cc=gregkh@suse.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox