From: Grant Likely <grant.likely@secretlab.ca>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] powerpc/pci: Pull ppc32 PCI features into common
Date: Tue, 25 Aug 2009 23:46:43 -0600 [thread overview]
Message-ID: <fa686aa40908252246k5d76ee18rf3440d0225eba6d2@mail.gmail.com> (raw)
In-Reply-To: <1251253245-16616-1-git-send-email-galak@kernel.crashing.org>
On Tue, Aug 25, 2009 at 8:20 PM, Kumar Gala<galak@kernel.crashing.org> wrot=
e:
> Some of the PCI features we have in ppc32 we will need on ppc64
> platforms in the future. =A0These include support for:
>
> * ppc_md.pci_exclude_device
> * indirect config cycles
> * early config cycles
>
> We also simplified the logic in fake_pci_bus() to assume it will always
> get a valid pci_controller. =A0Since all current callers seem to pass it
> one.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Looks okay to me.
Acked-by: Grant Likely <grant.likely@secretlab.ca>
g.
prev parent reply other threads:[~2009-08-26 5:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 2:20 [PATCH] powerpc/pci: Pull ppc32 PCI features into common Kumar Gala
2009-08-26 2:23 ` Kumar Gala
2009-08-26 5:46 ` Grant Likely [this message]
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=fa686aa40908252246k5d76ee18rf3440d0225eba6d2@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=galak@kernel.crashing.org \
--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