From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
John Rigby <jrigby@freescale.com>
Subject: Re: [PATCH 2/3] powerpc: 5121: Add PCI support.
Date: Wed, 8 Oct 2008 10:15:20 -0600 [thread overview]
Message-ID: <fa686aa40810080915v38a1c40cs7cac3825ee5a7bac@mail.gmail.com> (raw)
In-Reply-To: <4800D7D4-28BC-435A-9858-8FAF41F38468@kernel.crashing.org>
On Wed, Oct 8, 2008 at 6:38 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Oct 7, 2008, at 4:13 PM, John Rigby wrote:
>
>> Uses mpc83xx_add_bridge in fsl_pci.c
>>
>> Adds second register tuple to pci node register property
>> as done for 83xx device trees in a previous patch.
>>
>> Signed-off-by: John Rigby <jrigby@freescale.com>
>> ---
>> arch/powerpc/boot/dts/mpc5121ads.dts | 3 ++-
>> arch/powerpc/platforms/512x/Kconfig | 2 ++
>> arch/powerpc/platforms/512x/mpc5121_ads.c | 10 ++++++++++
>> arch/powerpc/sysdev/fsl_pci.c | 4 ++--
>> 4 files changed, 16 insertions(+), 3 deletions(-)
>
> Acked-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Grant Likely <grant.likely@secretlab.ca>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-10-08 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 21:13 [PATCH 2/3] powerpc: 5121: Add PCI support John Rigby
2008-10-08 12:38 ` Kumar Gala
2008-10-08 16:15 ` Grant Likely [this message]
2008-10-10 3:42 ` Kumar Gala
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 19:00 [PATCH 0/3] MPC5121 add pci support John Rigby
2008-10-07 19:00 ` [PATCH 1/3] powerpc: 83xx: pci: Remove need for get_immrbase from mpc83xx_add_bridge John Rigby
2008-10-07 19:00 ` [PATCH 2/3] powerpc: 5121: Add PCI support John Rigby
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=fa686aa40810080915v38a1c40cs7cac3825ee5a7bac@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--cc=jrigby@freescale.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).