From: Alex Chiang <achiang@hp.com>
To: jbarnes@virtuousgeek.org, lenb@kernel.org
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: [PATCH 0/3] ACPI/PCI Hotplug: acpiphp cleanup
Date: Fri, 10 Jul 2009 13:42:33 -0600 [thread overview]
Message-ID: <20090710193601.30165.62311.stgit@bob.kio> (raw)
Hi Len, Jesse,
I'd like to have this patch series considered for the current release
because it clarifies some usage of the new interface acpi_get_pci_dev()
that was also introduced in this release cycle.
The short story is, acpi_get_pci_dev() doesn't always return a struct
pci_dev, because a PCI root bridge may not have an associated pci_dev on
platforms with non-materialized root bridges.
See this patch for more:
http://patchwork.kernel.org/patch/32613/
I had to export acpi_pci_root to accomplish my goal, but it did result
in a nice net cleanup in acpiphp.
It should probably go through Jesse's tree, but needs Len's ACK for
the acpi_pci_root bit.
Thanks.
/ac
---
Alex Chiang (3):
ACPI: export acpi_pci_root and friends
PCI Hotplug: acpiphp: find bridges the easy way
PCI Hotplug: convert acpi_pci_detect_ejectable() to take an acpi_handle
drivers/acpi/pci_root.c | 17 +------
drivers/pci/hotplug/acpi_pcihp.c | 9 +---
drivers/pci/hotplug/acpiphp_glue.c | 92 +++++++++---------------------------
drivers/pci/hotplug/pciehp_acpi.c | 5 +-
include/acpi/acpi_bus.h | 14 +++++
include/linux/pci_hotplug.h | 2 -
6 files changed, 47 insertions(+), 92 deletions(-)
next reply other threads:[~2009-07-10 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-10 19:42 Alex Chiang [this message]
2009-07-10 19:42 ` [PATCH 1/3] ACPI: export acpi_pci_root and friends Alex Chiang
2009-07-10 19:42 ` [PATCH 2/3] PCI Hotplug: acpiphp: find bridges the easy way Alex Chiang
2009-07-10 19:42 ` [PATCH 3/3] PCI Hotplug: convert acpi_pci_detect_ejectable() to take an acpi_handle Alex Chiang
2009-07-14 19:27 ` [PATCH 0/3] ACPI/PCI Hotplug: acpiphp cleanup Jesse Barnes
2009-07-14 20:04 ` Alex Chiang
2009-07-14 20:32 ` Jesse Barnes
2009-07-14 20:33 ` Jesse Barnes
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=20090710193601.30165.62311.stgit@bob.kio \
--to=achiang@hp.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.