[PATCH -v2 00/11] PCI: pci_host_bridge related cleanup

[Yinghai Lu]

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/