Different DMI_BOARD_NAME's are affected by this reboot issue as well,
so we want to expand the quirk coverage by removing the DMI_BOARD_NAME
match.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=54051
BugLink: https://bugs.launchpad.net/bugs/488319
Signed-off-by: Pascal de Bruijn <pas...@unilogicnetworks.net>
---
arch/x86/kernel/reboot.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c
index 76fa1e9..33b6362 100644
--- a/arch/x86/kernel/reboot.c
+++ b/arch/x86/kernel/reboot.c
@@ -299,7 +299,6 @@ static struct dmi_system_id __initdata
reboot_dmi_table[] = {
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Dell Inc."),
DMI_MATCH(DMI_PRODUCT_NAME, "OptiPlex 760"),
- DMI_MATCH(DMI_BOARD_NAME, "0G919G"),
},
},
{ /* Handle problems with rebooting on Dell 2400's */
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
