The patch titled panasonic-laptop: depends on ACPI has been removed from the -mm tree. Its filename was panasonic-laptop-depends-on-acpi.patch This patch was dropped because it was merged into mainline or a subsystem tree The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: panasonic-laptop: depends on ACPI From: Randy Dunlap <randy.dunlap@xxxxxxxxxx> panasonic-laptop uses many acpi_*() functions so it should depend on ACPI; otherwise there are approximately 70 warnings/errors generated. Signed-off-by: Randy Dunlap <randy.dunlap@xxxxxxxxxx> Acked-by: Harald Welte <laforge@xxxxxxxxxxxx> Cc: Len Brown <lenb@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/misc/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff -puN drivers/misc/Kconfig~panasonic-laptop-depends-on-acpi drivers/misc/Kconfig --- a/drivers/misc/Kconfig~panasonic-laptop-depends-on-acpi +++ a/drivers/misc/Kconfig @@ -249,7 +249,7 @@ config MSI_LAPTOP config PANASONIC_LAPTOP tristate "Panasonic Laptop Extras" - depends on X86 && INPUT + depends on X86 && INPUT && ACPI depends on BACKLIGHT_CLASS_DEVICE ---help--- This driver adds support for access to backlight control and hotkeys _ Patches currently in -mm which might be from randy.dunlap@xxxxxxxxxx are docbook-fix-command-spacing.patch docs-fix-managementstyle-book-name.patch linux-next.patch fujitsu-laptop-fix-section-mismatch-warning.patch acpi-compal-laptop-use-rfkill-switch-subsystem-fix.patch genksyms-track-symbol-checksum-changes.patch genksyms-allow-to-ignore-symbol-checksum-changes.patch lkdtm-fix-for-config_scsi=n.patch e1000e-make-e1000e-default-to-the-same-kconfig-setting-as-e1000.patch gdth-fix-section-mismatch-warnings.patch esp-fix-section-mismatch-warning.patch mm-cleanup-to-make-remove_memory-arch-neutral-fix-fix.patch profile-likely-unlikely-macros.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html