Re: [RFC PATCH 0/3] PCI: allocate pci bus num range for bridge scan

From: Yinghai Lu
Date: Sun Jan 22 2012 - 14:22:35 EST


On Sat, Jan 21, 2012 at 2:24 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
>
> could be found at:
>        git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git for-pci-busn-alloc
>
>
>  arch/ia64/pci/pci.c              |    9 +
>  arch/powerpc/kernel/pci-common.c |   12 ++-
>  arch/x86/include/asm/topology.h  |    3 +-
>  arch/x86/pci/acpi.c              |   15 ++-
>  arch/x86/pci/bus_numa.c          |    8 +-
>  arch/x86/pci/common.c            |   11 +-
>  drivers/parisc/dino.c            |    9 +
>  drivers/parisc/lba_pci.c         |    8 +
>  drivers/pci/probe.c              |  298 +++++++++++++++++++++++++++++---------
>  drivers/pci/remove.c             |    1 +
>  include/linux/ioport.h           |    1 +
>  include/linux/pci.h              |    5 +
>  kernel/resource.c                |    8 +
>  13 files changed, 310 insertions(+), 78 deletions(-)

update the branch to have less change to other arch and add one patch
to separate
pci_scan_child_bus to two passes.

5cb2147: PCI: Seperate child bus scanning to two passes overall
0cfebdb: PCI: kill pci_fixup_parent_subordinate_busnr()
cd03e86: PCI: Allocate bus range instead of use max blindly
e3edd5b: PCI: Add iobusn_resource and insert root bus range to that tree.

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 | 427 ++++++++++++++++++++++++++++++--------
drivers/pci/remove.c | 1 +
include/linux/ioport.h | 1 +
include/linux/pci.h | 8 +
kernel/resource.c | 8 +
13 files changed, 395 insertions(+), 94 deletions(-)
--
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/