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@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Kokoris, Ioannis" <ioannis.kokoris@siemens-enterprise.com>
Subject: Re: [PATCH] P1021: set IReady in QE Microcode Upload
Date: Fri, 16 Mar 2012 10:21:12 -0500	[thread overview]
Message-ID: <AC087E7A-B7BC-43E5-948F-68AEB8251FD3@kernel.crashing.org> (raw)
In-Reply-To: <0154F680-D9F4-4CE1-BF5E-11884AD0ED4A@freescale.com>


On Nov 24, 2011, at 7:57 AM, Tabi Timur-B04825 wrote:

> On Nov 24, 2011, at 1:55 AM, Kumar Gala <galak@kernel.crashing.org> =
wrote:
>=20
>>>=20
>>> I'll have to check.  But this patch can't be applied as-is unless =
it's
>>> proven safe for all QE-enabled chips.
>>=20
>> Any update on trying this on a MPC8323?
>=20
> Haiying said it should be ok, but I haven't tried it yet.  I'll try it =
on Monday.

Did you ever test this?

- k=

  reply	other threads:[~2012-03-16 15:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 16:05 [PATCH] P1021: set IReady in QE Microcode Upload Kokoris, Ioannis
2011-11-11 16:39 ` Tabi Timur-B04825
2011-11-14  8:55   ` Kokoris, Ioannis
2011-11-16  3:02     ` Tabi Timur-B04825
2011-11-24  7:55       ` Kumar Gala
2011-11-24 13:57         ` Tabi Timur-B04825
2012-03-16 15:21           ` Kumar Gala [this message]
2012-03-16 16:07             ` Timur Tabi
2012-06-29 19:23               ` Kumar Gala
2012-06-29 19:26                 ` Timur Tabi
2012-07-02 18:19                 ` Timur Tabi
2012-07-10 12:24 ` 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=AC087E7A-B7BC-43E5-948F-68AEB8251FD3@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=B04825@freescale.com \
    --cc=ioannis.kokoris@siemens-enterprise.com \
    --cc=linux-kernel@vger.kernel.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).