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: Wed, 3 Dec 2014 11:59:11 +0100 [thread overview]
Message-ID: <201412031159.12055@pali> (raw)
In-Reply-To: <DD50BA4C-4E7C-4E69-9A79-52C2B577F580@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 1901 bytes --]
On Thursday 27 November 2014 19:08:04 Dmitry Torokhov wrote:
> On November 25, 2014 3:08:31 AM PST, "Pali Rohár"
<pali.rohar@gmail.com> wrote:
> >On Thursday 20 November 2014 00:29:49 Pali Rohár wrote:
> >> On Monday 17 November 2014 08:39:14 Pali Rohár wrote:
> >> > On Friday 14 November 2014 21:59:31 Dmitry Torokhov wrote:
> >> > > Hi Pali,
> >> > >
> >> > > On Friday, November 14, 2014 08:38:19 PM 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.
> >> > >
> >> > > Thank you for splitting the change, unfortunately it is
> >> > > now quite big to apply to 3.18. Any chance you could
> >> > > try implementing what I suggested in
> >> > > http://www.spinics.net/lists/linux-input/msg34029.html
> >> > > and then we can do the more comprehensive solution in
> >> > > 3.19.
> >> > >
> >> > > Thanks.
> >> >
> >> > Hello, I think that patches 1/7 and 5/7 could do that
> >> > job. I did not tested them alone (without other
> >> > patches), but if you think that two patches are ok for
> >> > 3.18 & stable I can test them...
> >>
> >> Dmitry, ping.
> >
> >Dmitry: ping again.
>
> Hi Pali,
>
> I'm on vacation and unfortunately connection here is
> horrendous so I likely won't be able to do anything until
> after 12/03.
>
> Sorry about that.
Hi Dmitry,
I tested that two patches 1/7 and 5/7 on top of 3.18 and it fixed
name of ALPS devices. Can you send those two patches to 3.18
queue (just remove comment about speed as without other patches
duplicate detection is still called)?
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2014-12-03 10:59 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 [this message]
2014-12-09 17:08 ` Pali Rohár
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=201412031159.12055@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).