From: Scott Wood <scottwood@freescale.com>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH 0/3 v2] Remove need for include/asm-ppc
Date: Mon, 20 Aug 2007 10:44:31 -0500 [thread overview]
Message-ID: <46C9B6DF.1000006@freescale.com> (raw)
In-Reply-To: <20070820103719.23f50f64@weaponx.rchland.ibm.com>
Josh Boyer wrote:
> On Mon, 20 Aug 2007 10:32:43 -0500
> Kumar Gala <galak@kernel.crashing.org> wrote:
>>Do we want to go and move stuff back out of arch/powerpc/kernel back
>>into arch/ppc/kernel? or just include files?
>
>
> What would be the point of doing that? I would think we want the
> opposite, in that we want to reuse as much of arch/powerpc during
> arch/ppc compiles as possible. Sort of shows how much is "left" to
> port.
The point would be to keep the two trees separate, so that one doesn't
need to worry about breaking arch/ppc when making a change to arch/powerpc.
-Scott
next prev parent reply other threads:[~2007-08-20 15:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-18 17:05 [PATCH 0/3 v2] Remove need for include/asm-ppc Kumar Gala
2007-08-18 17:07 ` [PATCH 1/3 v2][POWERPC] Remove old includes from arch/ppc Kumar Gala
2007-08-18 17:09 ` [PATCH 2/3 v2][POWERPC] Copy over headers from arch/ppc to arch/powerpc that we need Kumar Gala
2007-08-18 17:11 ` [PATCH 3/3 v2][POWERPC] Stop include asm-ppc when building ARCH=powerpc for ppc32 Kumar Gala
2007-08-20 5:54 ` Paul Mackerras
2007-08-20 5:57 ` Paul Mackerras
2007-08-20 15:29 ` Kumar Gala
2007-08-20 15:28 ` Kumar Gala
2007-08-20 6:00 ` [PATCH 0/3 v2] Remove need for include/asm-ppc David Gibson
2007-08-20 15:32 ` Kumar Gala
2007-08-20 15:37 ` Josh Boyer
2007-08-20 15:44 ` Scott Wood [this message]
2007-08-20 15:53 ` Josh Boyer
2007-08-20 22:11 ` Segher Boessenkool
2007-08-21 1:47 ` David Gibson
2007-08-21 2:47 ` Josh Boyer
2007-08-21 2:50 ` David Gibson
2007-08-21 12:05 ` Arnd Bergmann
2007-08-21 12:56 ` Josh Boyer
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=46C9B6DF.1000006@freescale.com \
--to=scottwood@freescale.com \
--cc=david@gibson.dropbear.id.au \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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.