PCI hotplug: acpiphp should be linked after vendor drivers
authorMatthew Garrett <mjg@redhat.com>
Mon, 26 Oct 2009 17:18:22 +0000 (13:18 -0400)
committerJesse Barnes <jbarnes@virtuousgeek.org>
Wed, 4 Nov 2009 16:47:14 +0000 (08:47 -0800)
commit3368dd29586c6460b629ac5b4f6b86a6fd3dd421
tree2af678adf59130741107b8f5f94f48aa78d25f26
parent17d67152793c43344930bda9b723c80186598aad
PCI hotplug: acpiphp should be linked after vendor drivers

As a followup to 71a082efc9fdc12068a3cee6cebb1330b00ebeee, it's conceivable
that some vendors may expose PCI hotplug functionality through both vendor
mechanisms and ACPI. The native mechanism will generally be a superset of
any functionality provided via ACPI, so the acpiphp driver should always
be initialised after any others. Change the link order such that acpiphp
will not be initialised until any other statically linked drivers have had
an opportunity to claim the hardware.

Signed-off-by: Matthew Garrett <mjg@redhat.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
drivers/pci/hotplug/Makefile