On Wed, Jan 14, 2015 at 08:31:27PM -0800, Yinghai Lu wrote: > During the fix https://bugzilla.kernel.org/show_bug.cgi?id=85491, > Bjorn suggest that we should clip the resources instead of just > reject them. > > We should only need first two for x86. others for related arches > to keep them consistent. > > -v2: only handle bridge resource, and add pci_claim_bridge_resource > in pci core code. > > Thanks > > Yinghai > > Yinghai Lu (10): > PCI: clip firmware assigned resource under parent bridge's > PCI, x86: clip firmware assigned resource under parent bridge's > PCI, alpha: clip firmware assigned resource under parent bridge's > PCI, frv: clip firmware assigned resource under parent bridge's > PCI, ia64: clip firmware assigned resource under parent bridge's > PCI, microblaze: clip firmware assigned resource under parent bridge's > PCI, mn10300: clip firmware assigned resource under parent bridge's > PCI, parisc: clip firmware assigned resource under parent bridge's > PCI, powerpc: clip firmware assigned resource under parent bridge's > PCI, sparc: clip firmware assigned resource under parent bridge's > > arch/alpha/kernel/pci.c | 8 +++-- > arch/frv/mb93090-mb00/pci-frv.c | 2 +- > arch/ia64/pci/pci.c | 48 +++++++++++++--------------- > arch/microblaze/pci/pci-common.c | 13 +++++++- > arch/mn10300/unit-asb2305/pci-asb2305.c | 2 +- > arch/mn10300/unit-asb2305/pci.c | 47 +++++++++++++-------------- > arch/powerpc/kernel/pci-common.c | 12 ++++++- > arch/sparc/kernel/pci.c | 5 ++- > arch/x86/pci/i386.c | 2 +- > drivers/parisc/lba_pci.c | 5 ++- > drivers/pci/bus.c | 39 +++++++++++++++++++++++ > drivers/pci/pci.h | 1 + > drivers/pci/setup-bus.c | 56 ++++++++++++++++++++++++++------- > include/linux/pci.h | 1 + > 14 files changed, 165 insertions(+), 76 deletions(-) Applied to for-linus for v3.19, thanks. This is significantly different from v1, so I didn't add acks and testing info from Helge and Wei. Bjorn -- 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
