The patch titled
input: i8042: add Dritek quirk for Acer TravelMate 660
has been added to the -mm tree. Its filename is
input-i8042-add-dritek-quirk-for-acer-travelmate-660.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: input: i8042: add Dritek quirk for Acer TravelMate 660
From: Bruno Prémont <bonbons@xxxxxxxxxxxxxxxxx>
The Acer TravelMate 660 series also requires the Dritek quirk to enable
the extra scancodes.
Signed-off-by: Bruno Prémont <bonbons@xxxxxxxxxxxxxxxxx>
Cc: Dmitry Torokhov <dtor@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
drivers/input/serio/i8042-x86ia64io.h | 7 +++++++
1 file changed, 7 insertions(+)
diff -puN drivers/input/serio/i8042-x86ia64io.h~input-i8042-add-dritek-quirk-for-acer-travelmate-660 drivers/input/serio/i8042-x86ia64io.h
--- a/drivers/input/serio/i8042-x86ia64io.h~input-i8042-add-dritek-quirk-for-acer-travelmate-660
+++ a/drivers/input/serio/i8042-x86ia64io.h
@@ -331,6 +331,13 @@ static struct dmi_system_id __initdata i
},
},
{
+ .ident = "Acer TravelMate 660",
+ .matches = {
+ DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "TravelMate 660"),
+ },
+ },
+ {
.ident = "Acer TravelMate 2490",
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
_
Patches currently in -mm which might be from bonbons@xxxxxxxxxxxxxxxxx are
input-i8042-move-dritek-quirk-so-it-also-gets-applied-on-resume.patch
input-i8042-add-dritek-quirk-for-acer-travelmate-660.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
