public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 18:17:25 -0700	[thread overview]
Message-ID: <44989E25.3090402@goop.org> (raw)
In-Reply-To: <4498958B.504@vmware.com>

Zachary Amsden wrote:
> This is cleaner than the patches I sent in March, although we want to 
> re-use parts of the mach-default code, not replace it entirely.  Hence 
> my interest in the multi-subarch generic kernel.  I'd be glad to look 
> into it.
In my current Xen patch, I split the mach-default/setup.c into setup.c 
and setup-memory.c; Xen uses setup.c as-is, and then provides its own 
setup-xen.c.  That solves my immediate problem, but I don't know if it 
generalizes enough; certainly factoring default/setup.c into a cluster 
of reusable setup-*.c pieces is a pretty lightweight way of reusing 
those pieces.

    J

  reply	other threads:[~2006-06-21  1:17 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
2006-06-21  0:40     ` Zachary Amsden
2006-06-21  1:17       ` Jeremy Fitzhardinge [this message]
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=44989E25.3090402@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