From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Zachary Amsden <zach@vmware.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Chris Wright <chrisw@sous-sol.org>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>,
jeremy@xensource.com
Subject: Re: [PATCH 2.6.17] Clean up and refactor i386 sub-architecture setup
Date: Tue, 20 Jun 2006 17:24:25 -0700 [thread overview]
Message-ID: <449891B9.3060409@goop.org> (raw)
In-Reply-To: <44988E08.9070000@vmware.com>
Zachary Amsden wrote:
> This looks awesome. Are there any plans to get these
> sub-architectures to work with the generic subarch? Seems the next
> logical step would be putting each mach-*/*.o into separated namespaces.
I haven't looked at that. This patch was intended to be a very simple
uncontroversial rearrangement, in preparation for the Xen subarch, and
to just clean up a corner of the kernel which seems to have gotten a bit
warty. Chris just sent me your patches from March which look like they
cover a lot of the same ground, but I haven't looked at them in detail yet.
J
next prev parent reply other threads:[~2006-06-21 0:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 23:42 [PATCH 2.6.17] Clean up and refactor i386 sub-architecture setup Jeremy Fitzhardinge
2006-06-21 0:08 ` Zachary Amsden
2006-06-21 0:22 ` Chris Wright
2006-06-21 0:24 ` Jeremy Fitzhardinge [this message]
2006-06-21 0:40 ` Zachary Amsden
2006-06-21 1:17 ` Jeremy Fitzhardinge
2006-06-21 1:24 ` Zachary Amsden
2006-06-21 1:32 ` Jeremy Fitzhardinge
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=449891B9.3060409@goop.org \
--to=jeremy@goop.org \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@xensource.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach@vmware.com \
/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