All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Ebling <kernelhacker@lineone.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: suggestions for new kernel hacking-HOWTO
Date: Sun, 26 Aug 2001 00:01:41 +1000	[thread overview]
Message-ID: <E15ae0N-0008Pa-00@localhost> (raw)
In-Reply-To: Your message of "23 Aug 2001 22:29:27 +0100." <998602169.405.21.camel@elixr.jfreak>

In message <998602169.405.21.camel@elixr.jfreak> you write:
> Hi all,
> 
> I am considering putting together a new, more in depth kernel hacking
> HOWTO.  
> 
> The existing HOWTO (by Rusty), although an excellent source of technical
> information does not contain much practical advice on how to get
> started.

This sounds fantastic!  I'd always hoped that my document would be a
starting point for something more substantial, yet it never happened
8(

One word of warning: beware tying it too closely to shifting
architecture.  In particular, the original HOWTO was aimed at pointing
experienced programmers in the right direction, not reading the code
to them.

Perhaps consider adding:

	Kernel Style
		Don't do it in the kernel
		Don't sprinkle ifdefs
		User interfaces: read/write better than ioctls
		Architecture specific code & portability
		GNU extensions

	Kernel Politics:
		Licencing
		How to get a patch in
		Who owns what code?

Hope that helps,
Rusty.
--
Premature optmztion is rt of all evl. --DK

  parent reply	other threads:[~2001-08-26 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23 21:29 suggestions for new kernel hacking-HOWTO Andrew Ebling
2001-08-24  6:27 ` Arnaldo Carvalho de Melo
2001-08-24 14:28 ` Pragnesh Sampat
2001-08-25 14:01 ` Rusty Russell [this message]
2001-08-25 18:09 ` Andreas Dilger

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=E15ae0N-0008Pa-00@localhost \
    --to=rusty@rustcorp.com.au \
    --cc=kernelhacker@lineone.net \
    --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.