From: Dave Jones <davej@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.5.21] i386 arch subdivision into machine types
Date: Mon, 10 Jun 2002 01:22:07 +0200 [thread overview]
Message-ID: <20020610012207.L13140@suse.de> (raw)
In-Reply-To: <200206091729.g59HTnv08471@localhost.localdomain>
On Sun, Jun 09, 2002 at 01:29:49PM -0400, James Bottomley wrote:
> This code rearranges the arch/i386 directory structure to allow for sliding
> additional non-pc hardware in here in an easily separable (and thus easily
> maintainable) fashion. The idea is that all the code for the particular
> problem hardware should be able to go in a separate directory with only
> additional build options in config.in.
Now that Linus has taken Patricks large reorganisation, I think we're
ready to start looking at this. I'll experiment with it a little when
I get around to syncing against 2.5.21
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
prev parent reply other threads:[~2002-06-09 23:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 17:29 [PATCH 2.5.21] i386 arch subdivision into machine types James Bottomley
2002-06-09 23:22 ` Dave Jones [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=20020610012207.L13140@suse.de \
--to=davej@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--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