On Thu, Jun 27, 2013 at 12:21 PM, <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > The patch below does not apply to the 3.9-stable tree. > If someone wants it applied there, or to any other stable or longterm > tree, then please email the backport, including the original git commit > id to <stable@xxxxxxxxxxxxxxx>. > > thanks, > > greg k-h > > ------------------ original commit in Linus's tree ------------------ > > From 94add0f82469fa3c4ff978d03a34da90813c819d Mon Sep 17 00:00:00 2001 > From: Jiang Liu <jiang.liu@xxxxxxxxxx> > Date: Sun, 23 Jun 2013 00:59:55 +0200 > Subject: [PATCH] ACPI / dock: Initialize ACPI dock subsystem upfront > > Commit 3b63aaa70e1 (PCI: acpiphp: Do not use ACPI PCI subdriver > mechanism) introduced an ACPI dock support regression, because it > changed the relative initialization order of the ACPI dock subsystem > and the ACPI-based PCI hotplug (acpiphp). > > Namely, the ACPI dock subsystem has to be initialized before > acpiphp_enumerate_slots() is first run, which after commit > 3b63aaa70e1 happens during the initial enumeration of the PCI > hierarchy triggered by the initial ACPI namespace scan in > acpi_scan_init(). For this reason, the dock subsystem has to be > initialized before the initial ACPI namespace scan in > acpi_scan_init(). > > To make that happen, modify the ACPI dock subsystem to be > non-modular and add the invocation of its initialization routine, > acpi_dock_init(), to acpi_scan_init() directly before the initial > namespace scan. > > [rjw: Changelog, removal of dock_exit().] > References: https://bugzilla.kernel.org/show_bug.cgi?id=59501 > Reported-and-tested-by: Alexander E. Patrakov <patrakov@xxxxxxxxx> > Tested-by: Illya Klymov <xanf@xxxxxxx> > Signed-off-by: Jiang Liu <jiang.liu@xxxxxxxxxx> > Acked-by: Yinghai Lu <yinghai@xxxxxxxxxx> > Cc: 3.9+ <stable@xxxxxxxxxxxxxxx> should only need for 3.10. as 3.9 can still have acpiphp as module. Thanks Yinghai -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html