public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale•com>
To: Scott Wood <scottwood@freescale•com>
Cc: Wood Scott-B07421 <B07421@freescale•com>,
	Zhao Chenhui-B35336 <B35336@freescale•com>,
	"linux-mmc@vger•kernel.org" <linux-mmc@vger•kernel.org>,
	Zhang Haijun-B42677 <B42677@freescale•com>,
	Wrobel Heinz-R39252 <r39252@freescale•com>,
	Fleming Andy-AFLEMING <afleming@freescale•com>,
	"cbouatmailru@gmail•com" <cbouatmailru@gmail•com>,
	"cjb@laptop•org" <cjb@laptop•org>,
	"linuxppc-dev@lists•ozlabs.org" <linuxppc-dev@lists•ozlabs.org>
Subject: Re: [PATCH V3] powerpc/85xx: Add support for 85xx cpu type detection
Date: Tue, 16 Jul 2013 18:54:25 -0500	[thread overview]
Message-ID: <1374018865.8183.349@snotra> (raw)
In-Reply-To: <1373994129.8183.330@snotra> (from scottwood@freescale.com on Tue Jul 16 12:02:09 2013)

On 07/16/2013 12:02:09 PM, Scott Wood wrote:
> On 07/16/2013 03:46:44 AM, Zhang Haijun-B42677 wrote:
>> Hi, scott
>>=20
>> Need I change something?
>> I have some patches depend on this.
>> Expect your advice.
>>=20
>> Thanks.
>>=20
>> Regards
>> Haijun.
>=20
> It looks OK; go ahead and send the patches that depend on it.

Actually, could you add p2040, p4040, p4080, p5021, and any other =20
missing ones you notice (lots of e500v2 P1/P2 chips are missing too)?

At the very least p2040 and p5021 ought to be there if you're using =20
this to check for p2041/p5040 errata, since they're basically the same =20
chip and thus have the same errata.

-Scott=

  reply	other threads:[~2013-07-16 23:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-11  0:23 [PATCH V3] powerpc/85xx: Add support for 85xx cpu type detection Haijun Zhang
2013-07-16  8:46 ` Zhang Haijun-B42677
2013-07-16 17:02   ` Scott Wood
2013-07-16 23:54     ` Scott Wood [this message]
2013-07-17  2:34       ` Zhang Haijun-B42677

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=1374018865.8183.349@snotra \
    --to=scottwood@freescale$(echo .)com \
    --cc=B07421@freescale$(echo .)com \
    --cc=B35336@freescale$(echo .)com \
    --cc=B42677@freescale$(echo .)com \
    --cc=afleming@freescale$(echo .)com \
    --cc=cbouatmailru@gmail$(echo .)com \
    --cc=cjb@laptop$(echo .)org \
    --cc=linux-mmc@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=r39252@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