From: Michael Ellerman <michael@ellerman.id.au>
To: Jin Zhengxiong <Jason.Jin@freescale.com>
Cc: Olof Johannsson <olof@lixom.net>,
Gala Kumar <kumar.gala@freescale.com>,
linuxppc-dev@ozlabs.org
Subject: RE: [PATCH 1/4] powerpc: fsl_msi doesn't need it's own of_node
Date: Thu, 17 Jul 2008 21:53:44 +1000 [thread overview]
Message-ID: <1216295624.16655.2.camel@localhost> (raw)
In-Reply-To: <CC27DED0F8F39E48A7E75FD768688B7AAC731A@zch01exm27.fsl.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 418 bytes --]
On Thu, 2008-07-17 at 18:48 +0800, Jin Zhengxiong wrote:
> Ack, Tested the patch set on Freescale board and working good.
> Thanks
Thanks for testing.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-07-17 11:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 14:46 [PATCH 1/4] powerpc: fsl_msi doesn't need it's own of_node Michael Ellerman
2008-07-15 14:46 ` [PATCH 2/4] powerpc: Split-out common MSI bitmap logic into msi_bitmap.c Michael Ellerman
2008-07-15 14:46 ` [PATCH 3/4] powerpc: Convert the FSL MSI code to use msi_bitmap Michael Ellerman
2008-07-15 14:46 ` [PATCH 4/4] powerpc: Convert the MPIC " Michael Ellerman
2008-07-17 10:48 ` [PATCH 1/4] powerpc: fsl_msi doesn't need it's own of_node Jin Zhengxiong
2008-07-17 11:53 ` Michael Ellerman [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-05 23:10 Michael Ellerman
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=1216295624.16655.2.camel@localhost \
--to=michael@ellerman.id.au \
--cc=Jason.Jin@freescale.com \
--cc=kumar.gala@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
/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).