From: Dave Jones <davej@suse.de>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: mochel@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] i386 arch subdivision into machine types for 2.5.15
Date: Sun, 12 May 2002 00:14:47 +0200 [thread overview]
Message-ID: <20020512001447.D30904@suse.de> (raw)
In-Reply-To: <200205112206.g4BM6Dp13365@localhost.localdomain>
On Sat, May 11, 2002 at 06:06:13PM -0400, James Bottomley wrote:
> This split is essentially the same as the one I did for 2.5.8 except that I've
> cleaned up setup_arch.h slightly (the other was, as I was told, "icky"). I
> didn't do any other alterations to setup.c because the projects list implies
> that Dave Jones and Patrick Mochel are going to be doing this, so I'll slide
> my changes in around this.
First batch of this work turned up in my tree in 2.5.14-dj2, seems to be
behaving well, so that should be going to Linus soon. With that out of
the way, (plus some other smaller split-up work like mtrr), the path
should be paved for x86 subarch support.
> I've pulled visws.c out of i386/pci and put it in i386/visws.c, since it's
> really specific to visws and doing this also allows me to simplify the
> i386/pci/Makefile.
Sounds ok. visws is after all, an x86 subarch. Though we should probably
get some input from the folks who are actually still maintaining this
out-of-tree. I believe they have a project at sourceforge with newer
visws code than whats in mainline.
Other than Patricks work, and yours, the only other bits that are poking
arch/i386 anytime soon are probably ACPI and possibly some further
splitting up by one of the IBM folks whose name I've currently forgotten.
Dave.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-11 22:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-11 22:06 [PATCH] i386 arch subdivision into machine types for 2.5.15 James Bottomley
2002-05-11 22:14 ` Dave Jones [this message]
2002-05-11 22:28 ` William Lee Irwin III
2002-05-11 22:32 ` Dave Jones
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=20020512001447.D30904@suse.de \
--to=davej@suse.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.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