From: Michael Ellerman <mpe@ellerman•id.au>
To: Scott Wood <scottwood@freescale•com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
Paul Mackerras <paulus@samba•org>
Subject: Re: [PATCH 0/8] powerpc/8xx: Getting rid of CONFIG_8xx
Date: Wed, 08 Apr 2015 13:25:58 +1000 [thread overview]
Message-ID: <1428463558.29968.0.camel@ellerman.id.au> (raw)
In-Reply-To: <1428442269.22867.467.camel@freescale.com>
On Tue, 2015-04-07 at 16:31 -0500, Scott Wood wrote:
> 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.
Yeah, I think we missed the boat on that one.
cheers
prev parent reply other threads:[~2015-04-08 3:25 UTC|newest]
Thread overview: 8+ 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 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
2015-04-08 3:25 ` Michael Ellerman [this message]
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=1428463558.29968.0.camel@ellerman.id.au \
--to=mpe@ellerman$(echo .)id.au \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=paulus@samba$(echo .)org \
--cc=scottwood@freescale$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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