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: Wed, 13 Nov 2013 13:41:14 -0600 [thread overview]
Message-ID: <1384371674.1403.164.camel@snotra.buserror.net> (raw)
In-Reply-To: <5283C51F.9090708@Freescale.com>
On Wed, 2013-11-13 at 12:29 -0600, Emil Medve wrote:
> Somebody gratuitously added a P1023 defconfig more then two years ago
> with the notion that P1023 is special due to its datapath and we're
> still one year out before we'll have the (P1023) datapath driver
> upstream. As of now this defconfig is just bit-rotting in the tree
> creating confusion. Let's just remove it for now and we'll deal with the
> entire e500v2_dpaa business when the datapath support will be upstreamed
Sure.
-Scott
next prev parent reply other threads:[~2013-11-13 19:41 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
[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 [this message]
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=1384371674.1403.164.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).