From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Greg KH <gregkh@suse.de>, linux-kernel@vger.kernel.org, greg@kroah.com
Subject: Re: [RFC] HOWTO do Linux kernel development - take 2
Date: Wed, 16 Nov 2005 18:40:21 +0100 [thread overview]
Message-ID: <20051116174021.GE24753@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <1132162089.21643.87.camel@hades.cambridge.redhat.com>
On Wed, 16 November 2005 17:28:09 +0000, David Woodhouse wrote:
> On Tue, 2005-11-15 at 13:05 -0800, Greg KH wrote:
> > - "Programming the 80386" by Crawford and Gelsinger [Sybek]
>
> Maybe, but on the whole I suspect we'd do well if fewer people were
> thinking about one particular legacy architecture when writing kernel
> code.
>
> Newbie kernel hackers ought to be working on something SMP, big-endian
> and 64-bit. Get into good habits right away.
And make their on-medium format the opposite from their hardware. It
is so much nicer if a missing conversion here and there _does_ cause
problems.
Jörn
--
Correctness comes second.
Features come third.
Performance comes last.
Maintainability is needed for all of them.
prev parent reply other threads:[~2005-11-16 17:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-15 21:05 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
2005-11-16 17:28 ` David Woodhouse
2005-11-16 17:38 ` Randy.Dunlap
2005-11-16 17:40 ` Jörn Engel [this message]
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=20051116174021.GE24753@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=dwmw2@infradead.org \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®