From: Zachary Amsden <zach@vmware.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
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:08:40 -0700 [thread overview]
Message-ID: <44988E08.9070000@vmware.com> (raw)
In-Reply-To: <44988803.5090305@goop.org>
Jeremy Fitzhardinge wrote:
> From: Jeremy Fitzhardinge <jeremy@xensource.com>
>
> Clean up and refactor i386 sub-architecture setup.
>
> This change moves all the code from the
> asm-i386/mach-*/setup_arch_pre/post.h headers, into
> arch/i386/mach-*/setup.c. mach-*/setup_arch_pre.h is renamed to
> setup_arch.h, and contains only things which should be in header
> files. It is purely code-motion; there should be no functional
> changes at all.
>
> Several functions in arch/i386/kernel/setup.c needed to be made
> non-static so that they're visible to the code in mach-*/setup.c.
> asm-i386/setup.h is used to hold the prototypes for these functions.
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.
Zach
next prev parent reply other threads:[~2006-06-21 0:08 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 [this message]
2006-06-21 0:22 ` Chris Wright
2006-06-21 0:24 ` Jeremy Fitzhardinge
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=44988E08.9070000@vmware.com \
--to=zach@vmware.com \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=jeremy@xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.