linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
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:37:19 -0500	[thread overview]
Message-ID: <20070820103719.23f50f64@weaponx.rchland.ibm.com> (raw)
In-Reply-To: <A4E8D00C-87DB-4C59-A6C4-70D437ED9988@kernel.crashing.org>

On Mon, 20 Aug 2007 10:32:43 -0500
Kumar Gala <galak@kernel.crashing.org> wrote:

> 
> On Aug 20, 2007, at 1:00 AM, David Gibson wrote:
> 
> > On Sat, Aug 18, 2007 at 12:05:36PM -0500, Kumar Gala wrote:
> >> This patch series removes the need for include/asm-ppc in the  
> >> ARCH=powerpc
> >> build for ppc32.  They exist in the following git tree:
> >>
> >>   master.kernel.org:/pub/scm/linux/kernel/git/galak/powerpc.git  
> >> for-2.6.24
> >>
> >> posting here for everyone else to see.
> >>
> >> Updated with changes suggested by Arnd & Segher. (removal 82xx pci  
> >> header
> >> and moving some headers under platforms if not globally needed).
> >
> > Nice!  I'm hoping the next step after this is to do the other way
> > around - make ARCH=ppc builds independent of things in arch/powerpc or
> > include/asm-powerpc, which is almost the more important change.
> 
> Maybe, hadn't thought about that case.  One thing at a time :)
> 
> 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.

Also, making arch/ppc compile stand-alone again would be "wasted" work,
since it's going to die anyway.

josh

  reply	other threads:[~2007-08-20 15:37 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 [this message]
2007-08-20 15:44       ` Scott Wood
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=20070820103719.23f50f64@weaponx.rchland.ibm.com \
    --to=jwboyer@linux.vnet.ibm.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=galak@kernel.crashing.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).