linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Tabi Timur-B04825 <B04825@freescale.com>
Cc: "linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH 1/4] powerpc/85xx: Rename PowerPC core nodes to match other e500mc based .dts
Date: Thu, 1 Sep 2011 22:35:34 -0500	[thread overview]
Message-ID: <F94709B7-1623-4DAC-8BE7-98DB3ABEEDDB@kernel.crashing.org> (raw)
In-Reply-To: <CAOZdJXUfgkvCCgW-KEgGJ0wW+EyGnhf+=aLV7E4SsKBoztP7uQ@mail.gmail.com>


On Sep 1, 2011, at 5:33 PM, Tabi Timur-B04825 wrote:

> On Thu, Sep 1, 2011 at 2:26 PM, Kumar Gala <galak@kernel.crashing.org> =
wrote:
>> The P4080 silicon device tree was using PowerPC,4080 while the other
>> e500mc based SoCs used PowerPC,e500mc.  Use the core name to be
>> consistent going forward.
>=20
> Shouldn't we change the nodes for all e500 based device trees in one
> shot, instead of just the P4080?

I changed all the e500mc class to match what is used by everyone else.  =
The e500v1/e500v2 are use the same convention at this time so figured a =
separate patch can handle them.

- k=

  reply	other threads:[~2011-09-02  3:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-01 19:26 [PATCH 1/4] powerpc/85xx: Rename PowerPC core nodes to match other e500mc based .dts Kumar Gala
2011-09-01 20:42 ` Scott Wood
2011-09-01 22:34   ` Tabi Timur-B04825
2011-09-02  3:21   ` Kumar Gala
2011-09-02 17:52     ` Scott Wood
2011-09-02 18:29       ` Kumar Gala
2011-09-02 18:33         ` Scott Wood
2011-09-01 22:33 ` Tabi Timur-B04825
2011-09-02  3:35   ` Kumar Gala [this message]
2011-10-12  4:21 ` Kumar Gala

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=F94709B7-1623-4DAC-8BE7-98DB3ABEEDDB@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=B04825@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).