From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Kumar Gala" <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org, John Rigby <jrigby@freescale.com>
Subject: Re: [PATCH 0/3] MPC5121 add pci support
Date: Wed, 8 Oct 2008 10:14:51 -0600 [thread overview]
Message-ID: <fa686aa40810080914n508150bcva235ec85322ff5cf@mail.gmail.com> (raw)
In-Reply-To: <77D97C6B-7F07-45AA-98D0-EE4723E2ABAD@kernel.crashing.org>
On Wed, Oct 8, 2008 at 12:20 AM, Kumar Gala <galak@kernel.crashing.org> wrote:
>
> On Oct 7, 2008, at 2:00 PM, John Rigby wrote:
>
>> The following three patches add pci support for MPC5121
>> These got no NACKs back in August but they were not picked up
>> by anyone either.
>
> I'll look at picking up patches 1/3 and 3/3. I'll leave 2/3 to Grant.
Kumar, since both 1/3 and 2/3 touch fsl_pci.c, can you please pick up
2/3? It won't conflict with anything that I'm pushing. I'll post my
ack-by line.
g.
>
> - k
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-10-08 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
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
2008-10-07 19:00 ` [PATCH 3/3] powerpc: pci: 5121: Hide pci bridge John Rigby
2008-10-08 12:30 ` Kumar Gala
2008-10-08 12:35 ` [PATCH 1/3] powerpc: 83xx: pci: Remove need for get_immrbase from mpc83xx_add_bridge Kumar Gala
2008-10-08 6:20 ` [PATCH 0/3] MPC5121 add pci support Kumar Gala
2008-10-08 16:14 ` Grant Likely [this message]
2008-10-08 18:02 ` Kumar Gala
2008-10-08 15:29 ` Matt Sealey
2008-10-08 15:31 ` Grant Likely
2008-10-08 18:51 ` Matt Sealey
2008-10-08 18:56 ` 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=fa686aa40810080914n508150bcva235ec85322ff5cf@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).