From: Kumar Gala <galak@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] powerpc/pci: Pull ppc32 PCI features into common
Date: Tue, 25 Aug 2009 21:23:53 -0500 [thread overview]
Message-ID: <B3C29A62-ED34-4C07-8E5B-FF5C9ADE5F71@kernel.crashing.org> (raw)
In-Reply-To: <1251253245-16616-1-git-send-email-galak@kernel.crashing.org>
On Aug 25, 2009, at 9:20 PM, Kumar Gala wrote:
> Some of the PCI features we have in ppc32 we will need on ppc64
> platforms in the future. These 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. Since all current callers seem to pass it
> one.
>
> Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
> ---
> arch/powerpc/include/asm/machdep.h | 6 +-
> arch/powerpc/include/asm/pci-bridge.h | 35 +++++++---------
> arch/powerpc/kernel/pci-common.c | 70 ++++++++++++++++++++++++
> ++++++++
> arch/powerpc/kernel/pci_32.c | 71
> ---------------------------------
> 4 files changed, 89 insertions(+), 93 deletions(-)
Ben, Grant
This should just be a refresh of the patch mentioned here:
http://patchwork.ozlabs.org/patch/26648/
with the commit message cleaned up and rebased on 'next'.
- k
next prev parent reply other threads:[~2009-08-26 2:24 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 [this message]
2009-08-26 5:46 ` Grant Likely
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=B3C29A62-ED34-4C07-8E5B-FF5C9ADE5F71@kernel.crashing.org \
--to=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