The patch titled hp_accel: add quirks for HP ProBook 532x and HP Mini 5102 has been added to the -mm tree. Its filename is hp_accel-add-quirks-for-hp-probook-532x-and-hp-mini-5102.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://userweb.kernel.org/~akpm/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: hp_accel: add quirks for HP ProBook 532x and HP Mini 5102 From: Takashi Iwai <tiwai@xxxxxxx> Added missing axis-mapping for HP ProBook 532x and HP Mini 5102. Signed-off-by: Takashi Iwai <tiwai@xxxxxxx> Cc: Eric Piel <eric.piel@xxxxxxxxxxxxxxxx> Cc: <stable@xxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- drivers/hwmon/hp_accel.c | 2 ++ 1 file changed, 2 insertions(+) diff -puN drivers/hwmon/hp_accel.c~hp_accel-add-quirks-for-hp-probook-532x-and-hp-mini-5102 drivers/hwmon/hp_accel.c --- a/drivers/hwmon/hp_accel.c~hp_accel-add-quirks-for-hp-probook-532x-and-hp-mini-5102 +++ a/drivers/hwmon/hp_accel.c @@ -221,6 +221,8 @@ static struct dmi_system_id lis3lv02d_dm AXIS_DMI_MATCH("HPB442x", "HP ProBook 442", xy_rotated_left), AXIS_DMI_MATCH("HPB452x", "HP ProBook 452", y_inverted), AXIS_DMI_MATCH("HPB522x", "HP ProBook 522", xy_swap), + AXIS_DMI_MATCH("HPB532x", "HP ProBook 532", y_inverted), + AXIS_DMI_MATCH("Mini5102", "HP Mini 5102", xy_rotated_left_usd), { NULL, } /* Laptop models without axis info (yet): * "NC6910" "HP Compaq 6910" _ Patches currently in -mm which might be from tiwai@xxxxxxx are origin.patch linux-next.patch hp_accel-add-quirks-for-hp-probook-532x-and-hp-mini-5102.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