From: Peter Tyser <ptyser@xes-inc.com>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: linuxppc-dev@ozlabs.org, Dave Jiang <djiang@mvista.com>,
bluesmoke-devel@lists.sourceforge.net,
Doug Thompson <dougthompson@xmission.com>
Subject: Re: [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part
Date: Thu, 22 Jul 2010 10:19:35 -0500 [thread overview]
Message-ID: <1279811975.7232.8696.camel@petert> (raw)
In-Reply-To: <1279756992-29543-1-git-send-email-dbaryshkov@gmail.com>
Hi Dmitry,
On Thu, 2010-07-22 at 04:03 +0400, Dmitry Eremin-Solenikov wrote:
> Add definitions for PCI error detection device to be handled by (already
> existing) mpc85xx_edac.c driver.
>
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> ---
> arch/powerpc/boot/dts/mpc8536ds.dts | 7 +++++++
> arch/powerpc/boot/dts/mpc8536ds_36b.dts | 7 +++++++
> arch/powerpc/boot/dts/mpc8540ads.dts | 8 ++++++++
> arch/powerpc/boot/dts/mpc8541cds.dts | 14 ++++++++++++++
> arch/powerpc/boot/dts/mpc8544ds.dts | 7 +++++++
> arch/powerpc/boot/dts/mpc8548cds.dts | 14 ++++++++++++++
> arch/powerpc/boot/dts/mpc8555cds.dts | 14 ++++++++++++++
> arch/powerpc/boot/dts/mpc8560ads.dts | 7 +++++++
> arch/powerpc/boot/dts/mpc8568mds.dts | 7 +++++++
> arch/powerpc/boot/dts/sbc8548.dts | 7 +++++++
> arch/powerpc/boot/dts/sbc8560.dts | 7 +++++++
> arch/powerpc/boot/dts/socrates.dts | 7 +++++++
> arch/powerpc/boot/dts/stx_gp3_8560.dts | 7 +++++++
> arch/powerpc/boot/dts/tqm8540.dts | 10 ++++++++++
> arch/powerpc/boot/dts/tqm8541.dts | 7 +++++++
> arch/powerpc/boot/dts/tqm8548-bigflash.dts | 7 +++++++
> arch/powerpc/boot/dts/tqm8548.dts | 7 +++++++
> arch/powerpc/boot/dts/tqm8555.dts | 7 +++++++
> arch/powerpc/boot/dts/tqm8560.dts | 7 +++++++
> arch/powerpc/boot/dts/xpedite5200.dts | 7 +++++++
> arch/powerpc/boot/dts/xpedite5200_xmon.dts | 7 +++++++
> 21 files changed, 172 insertions(+), 0 deletions(-)
It looks like the dts files for the MPC8572-based boards weren't
included in this change despite patch 2/2 adding support for them. I'd
guess some other Freescale CPUs (eg P1020, P2020, etc) could be
supported by the same driver if you are inclined to add them to this
patch series.
Best,
Peter
next prev parent reply other threads:[~2010-07-22 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-22 0:03 [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Dmitry Eremin-Solenikov
2010-07-22 0:03 ` [PATCH 2/2] mpc85xx_edac: change to use new definitions for PCI EDAC regspace Dmitry Eremin-Solenikov
2010-07-22 15:38 ` Kumar Gala
2010-07-22 16:48 ` Dmitry Eremin-Solenikov
2010-07-22 18:25 ` Scott Wood
2010-07-22 18:40 ` Kumar Gala
2010-07-22 19:03 ` Dmitry Eremin-Solenikov
2010-07-22 19:15 ` Grant Likely
2010-07-22 19:25 ` Scott Wood
2010-07-22 19:10 ` Grant Likely
2010-07-24 0:20 ` Dmitry Eremin-Solenikov
2010-07-24 0:56 ` Grant Likely
2010-07-24 10:09 ` Dmitry Eremin-Solenikov
2010-07-22 15:19 ` Peter Tyser [this message]
2010-07-22 16:56 ` [PATCH 1/2] MPC85xx: add definitions for PCI error detection soc part Dmitry Eremin-Solenikov
2010-07-22 17:09 ` Peter Tyser
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=1279811975.7232.8696.camel@petert \
--to=ptyser@xes-inc.com \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=dbaryshkov@gmail.com \
--cc=djiang@mvista.com \
--cc=dougthompson@xmission.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).