From: Icenowy Zheng <icenowy@aosc.io>
To: Bastien Nocera <hadess@hadess.net>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Ondrej Jirman <megous@megous.com>
Cc: linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Add support for Goodix GT917S touch controller
Date: Fri, 28 Feb 2020 08:44:37 +0800 [thread overview]
Message-ID: <5E54F9AB-DC0C-48CD-99BA-62EBE6946495@aosc.io> (raw)
In-Reply-To: <e7857a3196443ac2a2a997bc9e4799d15168c527.camel@hadess.net>
于 2020年2月28日 GMT+08:00 上午1:51:54, Bastien Nocera <hadess@hadess.net> 写到:
>On Fri, 2020-02-28 at 00:07 +0800, Icenowy Zheng wrote:
>> This patchset introduces support for Goodix GT917S touch controller.
>>
>> The major difference with other touch controllers from Goodix is that
>> the ID string is no longer number-only (it contains a 'S'), so an
>> additional patch is introduced for migrating the ID to a string.
>>
>> Icenowy Zheng (3):
>> dt-bindings: input: touchscreen: add compatible string for Goodix
>> GT917S
>> Input: goodix - use string-based chip ID
>
>I'd put the dt-bindings patch after this change, but I don't think it
>matters much in this case.
>
>> Input: goodix - Add support for Goodix GT917S
>
>I didn't receive that last patch, whether on my address or the linux-
>input@ list.
My ISP works poorly recently and it's never sent.
I will sent v3 now including it.
>
>Cheers
--
使用 K-9 Mail 发送自我的Android设备。
prev parent reply other threads:[~2020-02-28 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 16:07 [PATCH v2 0/3] Add support for Goodix GT917S touch controller Icenowy Zheng
2020-02-27 16:08 ` [PATCH v2 1/3] dt-bindings: input: touchscreen: add compatible string for Goodix GT917S Icenowy Zheng
2020-02-27 16:08 ` [PATCH v2 2/3] Input: goodix - use string-based chip ID Icenowy Zheng
2020-02-27 17:50 ` Bastien Nocera
2020-02-27 17:51 ` [PATCH v2 0/3] Add support for Goodix GT917S touch controller Bastien Nocera
2020-02-28 0:44 ` Icenowy Zheng [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=5E54F9AB-DC0C-48CD-99BA-62EBE6946495@aosc.io \
--to=icenowy@aosc.io \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=hadess@hadess.net \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=megous@megous.com \
--cc=robh+dt@kernel.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).