All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <dwg@au1.ibm.com>
To: Josh Boyer <jwboyer@jdub.homelinux.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 0/3 v2] Remove need for include/asm-ppc
Date: Tue, 21 Aug 2007 12:50:15 +1000	[thread overview]
Message-ID: <20070821025015.GN15469@localhost.localdomain> (raw)
In-Reply-To: <20070820214730.1b3b6fd6@vader.jdub.homelinux.org>

On Mon, Aug 20, 2007 at 09:47:30PM -0500, Josh Boyer wrote:
> On Tue, 21 Aug 2007 11:47:07 +1000
> David Gibson <dwg@au1.ibm.com> wrote:
> 
> > On Mon, Aug 20, 2007 at 10:44:31AM -0500, Scott Wood wrote:
> > > 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.
> > 
> > Exactly so.  Having to be careful about not breaking arch/ppc when
> > doing cleanups for arch/powerpc is a pain in the bum.
> 
> How many times has that happened recently?  If it's fairly infrequent,

It's infrequent because I've shyed away from cleaning up shared files,
precisely because I'm afraid of breaking arch/ppc.

> then just do the split when you're doing the arch/powerpc cleanup.  I'm
> still not convinced that doing a wholesale split again is worth the
> effort.
> 
> But then again, I'm not opposed either.  Particularly if someone else
> is doing the work :).  It simply doesn't make tons of sense to my
> feeble little brain.  Seems like that time could be spent better
> elsewhere.
> 
> josh
> 

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist, thank you.  NOT _the_ _other_
				| _way_ _around_!
http://www.ozlabs.org/~dgibson

  reply	other threads:[~2007-08-21  3:02 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
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 [this message]
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=20070821025015.GN15469@localhost.localdomain \
    --to=dwg@au1.ibm.com \
    --cc=jwboyer@jdub.homelinux.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 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.