676b367: pcmcia: remove workaround for fixing pci parent bus subordinate ddbc547: PCI: Seperate child bus scanning to two passes overall c82fe6d: PCI: kill pci_fixup_parent_subordinate_busnr() 7bf1ff4: PCI: Allocate bus range instead of use max blindly 1e511be: PCI: Strict checking of valid range for bridge a433d03: PCI: Probe safe range that we can use for unassigned bridge. 7f45e65: PCI: Add pci_bus_extend/shrink_top() 6e8d9f1: PCI, parisc: Register busn_res for root buses aadaf33: PCI, powerpc: Register busn_res for root buses 10ba93b: PCI, ia64: Register busn_res for root buses 6663d7a: PCI, x86: Register busn_res for root buses f283aa2: PCI: Add busn_res tracking in core d20c7d9: PCI: Add busn_res operation functions 196dcc6: PCI: Add iobusn_resource 634a14b: Make %pR could handle bus resource with domain Set up iobusn_resource tree, and register bus number range to it. Later when need to find bus range, will try to allocate from the tree Need to test on arches other than x86. esp for ia64 and powerpc that support more than on peer root buses. could be found at: git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-busn-alloc -v2: according to Jesse, split to more small patches. -v3: address some request from Bjorn. like make use %pR for busn_res debug print out, and move the comment change with code change. -v4: fixes the problem about rescan that Bjorn found. Thanks Yinghai arch/ia64/pci/pci.c | 2 + arch/powerpc/kernel/pci-common.c | 7 +- arch/x86/include/asm/topology.h | 3 +- arch/x86/pci/acpi.c | 8 +- arch/x86/pci/bus_numa.c | 8 +- arch/x86/pci/common.c | 11 +- drivers/parisc/dino.c | 2 + drivers/parisc/lba_pci.c | 3 + drivers/pci/probe.c | 417 ++++++++++++++++++++++++++++++-------- drivers/pci/remove.c | 1 + drivers/pcmcia/yenta_socket.c | 75 ------- include/linux/ioport.h | 1 + include/linux/pci.h | 8 + kernel/resource.c | 8 + lib/vsprintf.c | 28 +++- 15 files changed, 410 insertions(+), 172 deletions(-) -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
