From: William Lee Irwin III <wli@holomorphy.com>
To: Dave Jones <davej@suse.de>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
mochel@osdl.org, linux-kernel@vger.kernel.org
Cc: gone@us.ibm.com
Subject: Re: [PATCH] i386 arch subdivision into machine types for 2.5.15
Date: Sat, 11 May 2002 15:28:53 -0700 [thread overview]
Message-ID: <20020511222853.GD32767@holomorphy.com> (raw)
In-Reply-To: <200205112206.g4BM6Dp13365@localhost.localdomain> <20020512001447.D30904@suse.de>
On Sun, May 12, 2002 at 12:14:47AM +0200, Dave Jones wrote:
> 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.
Patricia Gaughen (specifically for support of the NUMA-Q platform/subarch)
Cheers,
Bill
next prev parent reply other threads:[~2002-05-11 22:30 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
2002-05-11 22:28 ` William Lee Irwin III [this message]
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=20020511222853.GD32767@holomorphy.com \
--to=wli@holomorphy.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=davej@suse.de \
--cc=gone@us.ibm.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