All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: leroy christophe <christophe.leroy@c-s.fr>
Cc: Paul Mackerras <paulus@samba.org>,
	linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 0/8] powerpc/8xx: Getting rid of CONFIG_8xx
Date: Tue, 7 Apr 2015 16:31:09 -0500	[thread overview]
Message-ID: <1428442269.22867.467.camel@freescale.com> (raw)
In-Reply-To: <5523932C.8070303@c-s.fr>

On Tue, 2015-04-07 at 10:19 +0200, leroy christophe wrote:
> Le 25/03/2015 01:45, Scott Wood a écrit :
> > On Fri, 2015-03-13 at 10:34 +1100, Michael Ellerman wrote:
> >> You'll need to collect ACKs, or get the individual patches merged, and then we
> >> can take patch 8 through the powerpc tree once those are all in - probably for
> >> 4.2.
> > It looks like CONFIG_8xx is used a lot more than CONFIG_PPC_8xx, so it
> > would be less churn to get rid of the latter (plus, we also have
> > CONFIG_4xx, CONFIG_6xx, etc).  The only use of PPC_8xx I see outside
> > arch/powerpc is in drivers/watchdog/Kconfig.
> 
> Ok, we can do that. But when outside of arch/powerpc/, isn't is more 
> explicit with CONFIG_PPC_8xx rather that CONFIG_8xx ?

Yes, CONFIG_PPC_8xx is a better name, but churn and consistency matter
as well.

> Now that I have submitted the first set of patch, don't we have a risk 
> that now it is already merged by some other maintainers ?

Sigh.  I see a couple in linux-next.

-Scott

  reply	other threads:[~2015-04-07 21:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-12 15:24 [PATCH 0/8] powerpc/8xx: Getting rid of CONFIG_8xx Christophe Leroy
2015-03-12 15:24 ` Christophe Leroy
2015-03-12 15:24 ` Christophe Leroy
2015-03-12 20:20 ` Geert Uytterhoeven
2015-03-12 20:20   ` Geert Uytterhoeven
2015-03-12 20:20   ` Geert Uytterhoeven
2015-03-12 20:20   ` Geert Uytterhoeven
2015-03-12 20:20   ` Geert Uytterhoeven
2015-03-12 20:20   ` Geert Uytterhoeven
2015-03-12 23:34 ` Michael Ellerman
2015-03-25  0:45   ` Scott Wood
2015-03-25  1:31     ` Michael Ellerman
2015-04-07  8:19     ` leroy christophe
2015-04-07 21:31       ` Scott Wood [this message]
2015-04-08  3:25         ` Michael Ellerman

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=1428442269.22867.467.camel@freescale.com \
    --to=scottwood@freescale.com \
    --cc=christophe.leroy@c-s.fr \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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.