From: Scott Wood <scottwood@freescale.com>
To: Emil Medve <Emilian.Medve@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH V2] powerpc/85xx: Merge 85xx/p1023_defconfig into mpc85xx_smp_defconfig and mpc85xx_defconfig
Date: Tue, 12 Nov 2013 19:46:15 -0600 [thread overview]
Message-ID: <1384307175.1403.118.camel@snotra.buserror.net> (raw)
In-Reply-To: <5282B277.4090300@Freescale.com>
On Tue, 2013-11-12 at 16:57 -0600, Emil Medve wrote:
> Hello Scott,
>
>
> On 11/12/2013 04:04 PM, Scott Wood wrote:
> > On Mon, 2013-11-11 at 13:25 -0600, Lijun Pan wrote:
> >> mpc85xx_smp_defconfig and mpc85xx_defconfig already have CONFIG_P1023RDS=y.
> >> Merge CONFIG_P1023RDB=y and other relevant configurations into mpc85xx_smp_defconfig and mpc85_defconfig.
> >>
> >> Signed-off-by: Lijun Pan <Lijun.Pan@freescale.com>
> >> ---
> >> arch/powerpc/configs/85xx/p1023_defconfig | 188 ----------------------------
> >> arch/powerpc/configs/mpc85xx_defconfig | 18 +++
> >> arch/powerpc/configs/mpc85xx_smp_defconfig | 17 +++
> >> 3 files changed, 35 insertions(+), 188 deletions(-)
> >> delete mode 100644 arch/powerpc/configs/85xx/p1023_defconfig
> >
> > Are we still going to want to have one defconfig if and when we finally
> > get datapath support upstream? That's a lot of code to add to the 85xx
> > config just for this one chip.
>
> Yes. But for mpc85xx_/smp_defconfig the datapath support shouldn't be
> enabled by default given that just one SoC in that family has the
> datapath (and we don't plan to put it in another e500v2 based SoC). For
> regression/automation purposes config fragments should be used
Is there any way to specify a meta-config for p1023 (or e500v2-dpaa or
whatever) that says to combine mpc85xx_smp_defconfig with a dpaa
fragment? Do we have any config fragments in the tree so far?
-Scott
next prev parent reply other threads:[~2013-11-13 1:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-08 23:17 [PATCH] powerpc/85xx: Merge 85xx/p1023_defconfig into mpc85xx_smp_defconfig and mpc85xx_defconfig Lijun Pan
2013-11-11 10:41 ` Claudiu Manoil
2013-11-11 19:25 ` [PATCH V2] " Lijun Pan
2013-11-12 16:27 ` Kumar Gala
2013-11-12 20:13 ` Timur Tabi
2013-11-12 22:04 ` Scott Wood
2013-11-12 22:49 ` Roy Zang
2013-11-12 22:52 ` Scott Wood
2013-11-12 23:05 ` Roy Zang
2013-11-12 23:09 ` Scott Wood
[not found] ` <1384293891.1403.70.camel__45039.5534084693$1384293935$gmane$org@snotra.buserror.net>
2013-11-12 22:57 ` Emil Medve
2013-11-13 1:46 ` Scott Wood [this message]
[not found] ` <1384307175.1403.118.camel__32063.4016803981$1384307228$gmane$org@snotra.buserror.net>
2013-11-13 2:34 ` Emil Medve
2013-11-13 18:19 ` Scott Wood
2013-11-13 18:29 ` Emil Medve
2013-11-13 19:41 ` Scott Wood
2013-11-13 23:24 ` [PATCH v3] " Lijun Pan
2013-11-15 23:28 ` [PATCH v4] " Lijun Pan
2014-01-08 1:04 ` [v4] " Scott Wood
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=1384307175.1403.118.camel@snotra.buserror.net \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@freescale.com \
--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).