linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hui Wang <hui.wang@canonical.com>
To: Peter Hutterer <peter.hutterer@who-t.net>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
	"Xiaoxiao Liu" <xiaoxiao.liu-1@cn.alps.com>,
	dmitry.torokhov@gmail.com,
	"XiaoXiao Liu" <sliuuxiaonxiao@gmail.com>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Xiaojian Cao" <xiaojian.cao@cn.alps.com>,
	"zhangfp1@lenovo.com" <zhangfp1@lenovo.com>
Subject: Re: 答复: 答复: 答复: [PATCH] input: alps-fix the issue the special alps trackpoint do not work.
Date: Sat, 25 May 2019 09:33:46 +0800	[thread overview]
Message-ID: <721b91b0-f231-5f7d-a438-09dd85f63513@canonical.com> (raw)
In-Reply-To: <20190524105822.GA3358@jelly>


On 2019/5/24 下午6:58, Peter Hutterer wrote:
> On Fri, May 24, 2019 at 06:43:58PM +0800, Hui Wang wrote:
>> On 2019/5/24 下午5:37, Peter Hutterer wrote:
>>> On Fri, May 24, 2019 at 03:37:57PM +0800, Hui Wang wrote:
>>>>
>> OK, that is sth we need to do.  But anyway it is a bit risky to backport
>> that much code and the whole folder of quirks to libinput 1.10.4,  we need
>> to do lots of test to make sure there is no regression on other machines.
>>
>> Probably we only need to keep the quirks/30-vendor-alps.quirks to 1.10.4 and
>> drop other quirks, that will be better for our testing effort.
> might be worth looking at what is in 1.10.7, e.g.  a3b3e85c0e looks like it
> may be of interest. That one suggests the range on some ALPS devices is over
> 100, so testing with 5-25 may really not have had any effect.

Oh, looks exactly the same as our issue, will have a try with it.

Thanks,

Hui.


>
> Cheers,
>     Peter
>

  reply	other threads:[~2019-05-25  1:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20 11:01 [PATCH] input: alps-fix the issue the special alps trackpoint do not work XiaoXiao Liu
2019-05-21  1:07 ` 答复: " Xiaoxiao Liu
2019-05-21  2:26   ` Hui Wang
2019-05-21  9:46     ` Pali Rohár
2019-05-22  2:53       ` 答复: " Xiaoxiao Liu
2019-05-22  6:35         ` Pali Rohár
2019-05-22  7:30           ` 答复: " Xiaoxiao Liu
2019-05-22  7:40             ` Pali Rohár
2019-05-23  6:01               ` Peter Hutterer
2019-05-24  5:25                 ` Hui Wang
2019-05-24  5:36                   ` Peter Hutterer
2019-05-24  5:50                     ` Hui Wang
2019-05-24  7:26                       ` Pali Rohár
2019-05-24  7:37                         ` Hui Wang
2019-05-24  9:37                           ` Peter Hutterer
     [not found]                             ` <f0c2dff9-519e-d54d-4cd0-2be666656dc2@canonical.com>
2019-05-24 10:58                               ` Peter Hutterer
2019-05-25  1:33                                 ` Hui Wang [this message]
2019-05-24  9:32                         ` Peter Hutterer
2019-05-24  9:52                           ` 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=721b91b0-f231-5f7d-a438-09dd85f63513@canonical.com \
    --to=hui.wang@canonical.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=peter.hutterer@who-t.net \
    --cc=sliuuxiaonxiao@gmail.com \
    --cc=xiaojian.cao@cn.alps.com \
    --cc=xiaoxiao.liu-1@cn.alps.com \
    --cc=zhangfp1@lenovo.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).