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, 25 Mar 2015 12:31:44 +1100 [thread overview]
Message-ID: <1427247104.29319.2.camel@ellerman.id.au> (raw)
In-Reply-To: <1427244330.22867.76.camel@freescale.com>
On Tue, 2015-03-24 at 19:45 -0500, Scott Wood wrote:
> On Fri, 2015-03-13 at 10:34 +1100, Michael Ellerman wrote:
> > On Thu, 2015-03-12 at 16:24 +0100, Christophe Leroy wrote:
> > > Two config options exist to define powerpc MPC8xx:
> > > * CONFIG_PPC_8xx
> > > * CONFIG_8xx
> > > In addition, CONFIG_PPC_8xx also defines CONFIG_CPM1 as
> > > communication co-processor
> > >
> > > arch/powerpc/platforms/Kconfig.cputype has contained the following
> > > comment about CONFIG_8xx item for some years:
> > > "# this is temp to handle compat with arch=ppc"
> > >
> > > It looks like not many places still have that old CONFIG_8xx used,
> > > so it is likely to be a good time to get rid of it completely ?
> > >
> > > Patchset is composed of the following patches:
> > > [1/8] powerpc: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [2/8] um: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [3/8] video: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [4/8] net: freescale: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [5/8] tty: cpm_uart: replace CONFIG_8xx by CONFIG_CPM1
> > > [6/8] mtd: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [7/8] isdn: replace CONFIG_8xx by CONFIG_PPC_8xx
> > > [8/8] powerpc: get rid of CONFIG_8xx
> > >
> > > All but the last one are independant and can be applied in any
> > > order. Only the 8th one requires the first 7 patches to be applied.
> >
> > Sounds good.
> >
> > I only see 0, 4 and 7 on linuxppc-dev for some reason.
>
> I see them all in linuxppc-dev patchwork.
Odd.
> > 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.
Yeah fine by me.
cheers
next prev parent reply other threads:[~2015-03-25 1:31 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 [this message]
2015-04-07 8:19 ` leroy christophe
2015-04-07 21:31 ` Scott Wood
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=1427247104.29319.2.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
/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).