From: "Pali Rohár" <pali.rohar@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
Yunkang Tang <yunkang.tang@cn.alps.com>,
Vadim Klishko <vadim@cirque.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] Fixes for ALPS trackstick
Date: Tue, 9 Dec 2014 18:08:48 +0100 [thread overview]
Message-ID: <201412091808.49071@pali> (raw)
In-Reply-To: <1415993906-13307-1-git-send-email-pali.rohar@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1183 bytes --]
On Friday 14 November 2014 20:38:19 Pali Rohár wrote:
> This patch series fix detection and identifying trackstick on
> machines with ALPS devices. Last patch split trackstick and
> bare PS/2 mouse packets between dev2 and dev3 input devices
> which make sure that driver will send only trackstick data to
> trackstick input device.
>
> Pali Rohár (7):
> input: alps: Set correct name of psmouse device in
> alps_init() input: alps: Move trackstick detection to
> alps_hw_init_* input: alps: Move alps_dolphin_get_device_area
> into alps_hw_init_dolphin_v1
> input: alps: Use NULL instead dummy argument for
> alps_identify input: alps: Fix name, product and version of
> dev2 input device input: alps: Add sanity checks for non
> DualPoint devices input: alps: Do not report both trackstick
> and external PS/2 mouse data to one input device
>
> drivers/input/mouse/alps.c | 361
> +++++++++++++++++++++++++++++++-------------
> drivers/input/mouse/alps.h | 14 +-
> 2 files changed, 264 insertions(+), 111 deletions(-)
Hi Dmitry, now when 3.18 was released, can you review this patch
series for 3.19?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2014-12-09 17:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 19:38 [PATCH 0/7] Fixes for ALPS trackstick Pali Rohár
2014-11-14 19:38 ` [PATCH 1/7] input: alps: Set correct name of psmouse device in alps_init() Pali Rohár
2014-12-16 5:02 ` Dmitry Torokhov
2014-12-16 11:58 ` Pali Rohár
2014-12-20 8:53 ` Pali Rohár
2014-12-24 7:48 ` Pali Rohár
2015-01-08 17:58 ` Pali Rohár
2014-11-14 19:38 ` [PATCH 2/7] input: alps: Move trackstick detection to alps_hw_init_* Pali Rohár
2014-11-14 19:38 ` [PATCH 3/7] input: alps: Move alps_dolphin_get_device_area into alps_hw_init_dolphin_v1 Pali Rohár
2014-11-14 19:38 ` [PATCH 4/7] input: alps: Use NULL instead dummy argument for alps_identify Pali Rohár
2014-11-14 19:38 ` [PATCH 5/7] input: alps: Fix name, product and version of dev2 input device Pali Rohár
2015-01-12 0:30 ` Dmitry Torokhov
2014-11-14 19:38 ` [PATCH 6/7] input: alps: Add sanity checks for non DualPoint devices Pali Rohár
2015-01-12 0:31 ` Dmitry Torokhov
2015-01-13 7:50 ` Pali Rohár
2014-11-14 19:38 ` [PATCH 7/7] input: alps: Do not report both trackstick and external PS/2 mouse data to one input device Pali Rohár
2014-11-14 20:59 ` [PATCH 0/7] Fixes for ALPS trackstick Dmitry Torokhov
2014-11-17 7:39 ` Pali Rohár
2014-11-19 23:29 ` Pali Rohár
2014-11-25 11:08 ` Pali Rohár
2014-11-27 18:08 ` Dmitry Torokhov
2014-12-03 10:59 ` Pali Rohár
2014-12-09 17:08 ` Pali Rohár [this message]
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=201412091808.49071@pali \
--to=pali.rohar@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vadim@cirque.com \
--cc=yunkang.tang@cn.alps.com \
/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).