diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2015-05-29 17:09:39 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-05-29 17:09:39 -0700 |
commit | aaa20fc23341be3df7b17810e330f12244abcf29 (patch) | |
tree | 2c637d9ef87a6595beacc8ff556705db7bf071b7 /drivers/pcmcia/i82365.c | |
parent | 1be44e234b672eadbf1d96eb172ef21f5ff6a2c9 (diff) | |
parent | dc4fdaf0e4839109169d8261814813816951c75f (diff) | |
download | linux-stable-aaa20fc23341be3df7b17810e330f12244abcf29.tar.gz linux-stable-aaa20fc23341be3df7b17810e330f12244abcf29.tar.bz2 linux-stable-aaa20fc23341be3df7b17810e330f12244abcf29.zip |
Merge tag 'acpi-pci-4.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull PCI / ACPI fix from Rafael Wysocki:
"This fixes a bug uncovered by a recent driver core change that
modified the implementation of the ACPI_COMPANION_SET() macro to
strictly rely on its second argument to be either NULL or a valid
pointer to struct acpi_device.
As it turns out, pcibios_root_bridge_prepare() on x86 and ia64 works
with the assumption that the only code path calling pci_create_root_bus()
is pci_acpi_scan_root() and therefore the sysdata argument passed to
it will always match the expectations of pcibios_root_bridge_prepare().
That need not be the case, however, and in particular it is not the
case for the Xen pcifront driver that passes a pointer to its own
private data strcture as sysdata to pci_scan_bus_parented() which then
passes it to pci_create_root_bus() and it ends up being used incorrectly
by pcibios_root_bridge_prepare()"
* tag 'acpi-pci-4.1-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
PCI / ACPI: Do not set ACPI companions for host bridges with parents
Diffstat (limited to 'drivers/pcmcia/i82365.c')
0 files changed, 0 insertions, 0 deletions