From: "Adrien Vergé" <adrienverge@gmail.com>
To: Benjamin Tissoires <benjamin.tissoires@gmail.com>,
Oliver Neukum <oneukum@suse.com>, Jiri Kosina <jikos@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Logan Gunthorpe" <logang@deltatee.com>,
"Hans de Goede" <hdegoede@redhat.com>,
"Vincent Palatin" <vpalatin@chromium.org>,
"Adrien Vergé" <adrienverge@gmail.com>,
"Macpaul Lin" <macpaul@gmail.com>,
"Adel Gadllah" <adel.gadllah@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: [PATCH v5 0/2] Fixes for ELAN touchscreens
Date: Tue, 1 Dec 2015 19:56:46 +0100 [thread overview]
Message-ID: <1448996208-19713-1-git-send-email-adrienverge@gmail.com> (raw)
In-Reply-To: <1448165164-11398-1-git-send-email-adrienverge@gmail.com>
This is the fifth version of a patchset which originally aimed to fix a buggy
touchscreen from ELAN Microelectronics.
Changes since v4:
- Cast HID_ANY_ID to an __u16 so to keep gcc happy on AVR32 arch.
Changes since v3:
- Use HID_ANY_ID to define a vendor-ID-global quirk, as suggested by
Benjamin Tissoires.
Changes since v2:
- Apply ALWAYS_POLL quirk to all ELAN devices by default, as suggested by
Jiri Kosina and Oliver Neukum.
Adrien Vergé (2):
USB: quirks: Fix another ELAN touchscreen
USB: quirks: Apply ALWAYS_POLL to all ELAN devices
drivers/hid/hid-ids.h | 5 -----
drivers/hid/usbhid/hid-quirks.c | 9 +++------
drivers/usb/core/quirks.c | 3 +++
3 files changed, 6 insertions(+), 11 deletions(-)
--
2.4.3
next prev parent reply other threads:[~2015-12-01 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 4:06 [PATCH] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-11-23 14:52 ` Jiri Kosina
2015-11-23 17:37 ` Adrien Vergé
2015-11-24 7:29 ` Oliver Neukum
2015-11-23 17:43 ` [PATCH v2] " Adrien Vergé
2015-11-24 13:49 ` [PATCH v3 0/2] Fixes for ELAN touchscreens Adrien Vergé
2015-11-24 13:49 ` [PATCH v3 1/2] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-11-24 13:49 ` [PATCH v3 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
2015-11-24 14:11 ` Benjamin Tissoires
2015-11-24 14:34 ` Adrien Vergé
2015-11-24 15:02 ` [PATCH v4 0/2] Fixes for ELAN touchscreens Adrien Vergé
2015-11-24 15:02 ` [PATCH v4 1/2] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-11-24 15:02 ` [PATCH v4 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
2015-11-24 16:11 ` Benjamin Tissoires
2015-11-24 16:41 ` kbuild test robot
2015-12-01 18:21 ` Greg Kroah-Hartman
2015-12-01 18:56 ` Adrien Vergé [this message]
2015-12-01 18:56 ` [PATCH v5 1/2] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-12-01 18:56 ` [PATCH v5 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
[not found] ` <1448996208-19713-3-git-send-email-adrienverge-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-12-01 22:09 ` Jiri Kosina
2015-12-01 22:11 ` Greg Kroah-Hartman
2015-12-02 8:53 ` Adrien Vergé
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1448996208-19713-1-git-send-email-adrienverge@gmail.com \
--to=adrienverge@gmail.com \
--cc=adel.gadllah@gmail.com \
--cc=benjamin.tissoires@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=macpaul@gmail.com \
--cc=oneukum@suse.com \
--cc=vpalatin@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).