From: "benjamin.tissoires" <benjamin.tissoires@gmail.com>
To: "benjamin.tissoires" <benjamin.tissoires@gmail.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Henrik Rydberg <rydberg@euromail.se>,
Jiri Kosina <jkosina@suse.cz>, Stephane Chatty <chatty@enac.fr>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [patch 0/5] Autohandling of multitouch devices through hid-multitouch
Date: Tue, 6 Mar 2012 17:57:01 +0100 [thread overview]
Message-ID: <1331053026-21272-1-git-send-email-benjamin.tissoires@gmail.com> (raw)
Hi Guys,
In this patch series, I introduce 1 trivial patch plus 4 patches that need review I think:
- the first is trivial (I missed it this morning, sorry)
- the second fixes a problem detected with LG panels. The detection of the end of the
report was not accurate, and needed to be rewritten. I'm worried about it because I got
warnings under Ubuntu for this patch (-Warray-bounds) whereas I don't get any warnings
under Fedora.
- the third should not be a problem as it relies on the presence of the QUIRK_MULTITOUCH
and will impact only unknown devices.
- the fourth worries me more. I introduce changes in hid_device, and I'd like to have your opinion.
- Then, the last one allows us to be compliant with Microsoft's description for Win 7 devices.
Cheers,
Benjamin
PS: Thanks Henrik and Jiri for the series of this morning.
next reply other threads:[~2012-03-06 16:57 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 16:57 benjamin.tissoires [this message]
2012-03-06 16:57 ` [PATCH 1/5] HID: multitouch: add support for eGalax 0x722a benjamin.tissoires
2012-03-09 12:29 ` Jiri Kosina
2012-03-10 6:31 ` Benjamin Tissoires
2012-03-12 12:40 ` Jiri Kosina
2012-03-12 12:40 ` Jiri Kosina
2012-03-12 13:02 ` Henrik Rydberg
2012-03-06 16:57 ` [PATCH 2/5] HID: multitouch: fix handling of buggy reports descriptors for Dell ST2220T benjamin.tissoires
2012-03-12 10:25 ` Jiri Kosina
2012-03-06 16:57 ` [PATCH 3/5] HID: handle all multitouch devices through hid-multitouch benjamin.tissoires
2012-03-06 16:57 ` [PATCH 4/5] HID: autoload hid-multitouch as needed benjamin.tissoires
2012-03-07 21:36 ` Jiri Kosina
2012-03-08 10:57 ` Henrik Rydberg
2012-03-08 11:21 ` Stéphane Chatty
2012-03-08 11:21 ` Stéphane Chatty
2012-03-08 11:30 ` Henrik Rydberg
2012-03-08 11:30 ` Henrik Rydberg
2012-03-08 11:48 ` Stéphane Chatty
2012-03-08 11:48 ` Stéphane Chatty
2012-03-08 12:23 ` Henrik Rydberg
2012-03-08 12:23 ` Henrik Rydberg
2012-03-08 22:47 ` Stéphane Chatty
2012-03-08 22:47 ` Stéphane Chatty
2012-03-12 16:18 ` Jiri Kosina
2012-03-12 15:57 ` Jiri Kosina
2012-03-12 15:57 ` Jiri Kosina
2012-03-12 17:42 ` Marcel Holtmann
2012-03-12 17:42 ` Marcel Holtmann
2012-03-12 20:47 ` Stéphane Chatty
2012-03-12 20:47 ` Stéphane Chatty
2012-03-12 22:21 ` Jiri Kosina
2012-03-13 10:17 ` Stéphane Chatty
2012-03-13 10:17 ` Stéphane Chatty
2012-03-13 10:17 ` Stéphane Chatty
2012-03-13 16:13 ` Jiri Kosina
2012-03-13 16:13 ` Jiri Kosina
2012-03-13 18:14 ` Stéphane Chatty
2012-03-13 18:14 ` Stéphane Chatty
2012-03-13 18:14 ` Stéphane Chatty
2012-03-16 11:26 ` Jiri Kosina
2012-03-06 16:57 ` [PATCH 5/5] HID: multitouch: detect serial protocol benjamin.tissoires
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=1331053026-21272-1-git-send-email-benjamin.tissoires@gmail.com \
--to=benjamin.tissoires@gmail.com \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@euromail.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.