From: Scott Wood <scottwood@freescale.com>
To: siva kumar <jasivkumar@gmail.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Freescale P2020 CPU Freeze over PCIe abort signal
Date: Thu, 24 Jan 2013 19:03:13 -0600 [thread overview]
Message-ID: <1359075793.24865.21@snotra> (raw)
In-Reply-To: <CAJrcUeRfz3m_NcE+HaVA8_3bGGuwaTM0ocPc7SYnhVaEaJyF2w@mail.gmail.com> (from jasivkumar@gmail.com on Thu Jan 24 05:53:51 2013)
On 01/24/2013 05:53:51 AM, siva kumar wrote:
> Thank you Scott for the reply.
> May I know did u got out of this issue and can i get some brief on =20
> what
> changes they had suggested.
I wasn't the one that had the issue. Why not send an e-mail to Eran =20
Liberty?
-Scott
> On Thu, Jan 24, 2013 at 3:10 AM, Scott Wood <scottwood@freescale.com> =20
> wrote:
>=20
> > On 01/23/2013 11:41:26 AM, siva kumar wrote:
> >
> >> Hi ,
> >>
> >> Is there any update on this , am getting in to the same state .
> >> https://lists.ozlabs.org/**pipermail/linuxppc-dev/2010-**
> >> =20
> October/086680.html<https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-=
October/086680.html>
> >>
> >
> > Eran's initial comment of "This should probably go to the Freescale
> > support" seems right. You can reach Freescale support at
> > support@freescale.com.
> >
> > -Scott
> >
>=20
=
next prev parent reply other threads:[~2013-01-25 1:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 17:41 Freescale P2020 CPU Freeze over PCIe abort signal siva kumar
2013-01-23 21:40 ` Scott Wood
2013-01-24 11:53 ` siva kumar
2013-01-25 1:03 ` Scott Wood [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-07 12:30 Freescale P2020 / 85xx PCIe and Advance Error Reporting (AER) service problem Eran Liberty
2010-10-11 0:19 ` Benjamin Herrenschmidt
2010-10-11 10:21 ` Eran Liberty
2010-10-11 11:32 ` Benjamin Herrenschmidt
2010-10-17 19:24 ` Freescale P2020 CPU Freeze over PCIe abort signal Eran Liberty
2010-10-18 5:26 ` Bin Meng
2010-10-18 9:52 ` tiejun.chen
2010-10-18 11:44 ` Eran Liberty
2010-10-18 18:00 ` Eran Liberty
2010-10-19 16:53 ` Eran Liberty
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=1359075793.24865.21@snotra \
--to=scottwood@freescale.com \
--cc=jasivkumar@gmail.com \
--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).