From: Yinghai Lu <yinghai@kernel.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>
Subject: [PATCH -v2 00/11] PCI: pci_host_bridge related cleanup
Date: Mon, 27 Feb 2012 18:03:40 -0800 [thread overview]
Message-ID: <1330394631-28978-1-git-send-email-yinghai@kernel.org> (raw)
will add struct device dev into host_bridge struct.
also will add release support to make sure allocated resource get
freed during root bus removal.
The patches need to apply to pci/for-linus and pci/linux-next
because one patch that is needed only get into pci/for-linus only
could get from
git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-next
-v2: remove several null checking requested by Bjorn
64c033c: x86, PCI: Merge root info printing for nocrs path
690fe82: x86, PCI: Allocating pci_root_info for nocrs path
2f7ea95: x86, PCI: embed name acpi version pci_root_info struct
2f79741: x86, PCI: add host bridge resource release for using _CRS
698ed24: x86, PCI: break down get_current_resource()
5acc80e: PCI: add host bridge release support
6068c94: PCI: add generic device into pci_host_bridge struct
6d34e92: PCI: rename pci_host_bridge() to find_pci_root_bridge()
bd114df: x86, PCI: Fix memleak with get_current_resources
e92c582: x86, PCI: have own version for pcibios_bus_to_resource
56f109d: PCI: Separate host_bridge code out from probe.c
Thanks
Yinghai Lu
arch/x86/pci/acpi.c | 116 +++++++++++++++++++++++-----------
arch/x86/pci/amd_bus.c | 78 +++++++----------------
arch/x86/pci/broadcom_bus.c | 14 +---
arch/x86/pci/bus_numa.c | 86 +++++++++++++++++++-------
arch/x86/pci/bus_numa.h | 19 +++---
arch/x86/pci/i386.c | 14 ++++
drivers/pci/Makefile | 2 +-
drivers/pci/host-bridge.c | 97 +++++++++++++++++++++++++++++
drivers/pci/probe.c | 145 ++++++++++--------------------------------
include/linux/pci.h | 9 +++-
10 files changed, 334 insertions(+), 246 deletions(-)
create mode 100644 drivers/pci/host-bridge.c
next reply other threads:[~2012-02-28 2:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 2:03 Yinghai Lu [this message]
2012-02-28 2:03 ` [PATCH 01/11] PCI: Separate host_bridge code out from probe.c Yinghai Lu
2012-02-28 2:03 ` [PATCH 02/11] x86, PCI: have own version for pcibios_bus_to_resource Yinghai Lu
2012-02-28 2:03 ` [PATCH 03/11] x86, PCI: Fix memleak with get_current_resources Yinghai Lu
2012-02-28 2:03 ` [PATCH 04/11] PCI: rename pci_host_bridge() to find_pci_root_bridge() Yinghai Lu
2012-02-28 2:03 ` [PATCH 05/11] PCI: add generic device into pci_host_bridge struct Yinghai Lu
2012-02-28 2:03 ` [PATCH 06/11] PCI: add host bridge release support Yinghai Lu
2012-02-28 2:03 ` [PATCH 07/11] x86, PCI: break down get_current_resource() Yinghai Lu
2012-02-28 2:03 ` [PATCH 08/11] x86, PCI: add host bridge resource release for using _CRS Yinghai Lu
2012-02-28 2:03 ` [PATCH 09/11] x86, PCI: embed name acpi version pci_root_info struct Yinghai Lu
2012-02-28 2:03 ` [PATCH 10/11] x86, PCI: Allocating pci_root_info for nocrs path Yinghai Lu
2012-02-28 2:03 ` [PATCH 11/11] x86, PCI: Merge root info printing " Yinghai Lu
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=1330394631-28978-1-git-send-email-yinghai@kernel.org \
--to=yinghai@kernel.org \
--cc=bhelgaas@google.com \
--cc=jbarnes@virtuousgeek.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 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).