From: Kumar Gala <galak@kernel.crashing.org>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
Cc: devicetree-discuss@lists.ozlabs.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: PCI EDAC on MPC85xx
Date: Tue, 31 May 2011 13:41:04 -0500 [thread overview]
Message-ID: <7373D079-743D-4D49-BDC6-2BEAF14C43DF@kernel.crashing.org> (raw)
In-Reply-To: <20110531131737.GA29164@doriath.ww600.siemens.net>
On May 31, 2011, at 8:17 AM, Dmitry Eremin-Solenikov wrote:
> Hello,
>=20
> Long time ago (around July of 2010), I've reported a problem of =
binding
> pci error reporting driver to the hardware (See
> http://thread.gmane.org/gmane.linux.kernel.edac/181). Grant Likely has
> come with a patch to create platform devices (of_platform at that =
time),
> for device_nodes which have "compatible" properties
> (http://article.gmane.org/gmane.linux.ports.ppc.embedded/36981).
>=20
> The patch was not applied at that time and the problem still arises at
> 3.0-rc1. Should the patch in question be applied, or is there any new
> solution?
> Current version of that patch which I have in my tree is attached
> to this mail (no original signoff by Grant).
>=20
> --=20
> With best wishes
> Dmitry
>=20
> <0001-of-device-Register-children-with-a-compatible-value-.patch>
I think the desired solution here was to create a new node in the =
fsl_pci code that the edac code would bind against.
- k=
next prev parent reply other threads:[~2011-05-31 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 13:17 PCI EDAC on MPC85xx Dmitry Eremin-Solenikov
2011-05-31 18:41 ` Kumar Gala [this message]
2011-05-31 19:25 ` Dmitry Eremin-Solenikov
2011-05-31 19:12 ` Grant Likely
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=7373D079-743D-4D49-BDC6-2BEAF14C43DF@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=dbaryshkov@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linuxppc-dev@lists.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).