From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Bastien Nocera <hadess@hadess.net>,
Matthias Brugger <matthias.bgg@gmail.com>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v3 0/3] input: goodix - support Goodix gt5688
Date: Sat, 16 Feb 2019 23:07:06 -0800 [thread overview]
Message-ID: <20190217070527.GC148958@dtor-ws> (raw)
In-Reply-To: <cover.1550239328.git.agx@sigxcpu.org>
On Fri, Feb 15, 2019 at 03:11:50PM +0100, Guido Günther wrote:
> Besides the support for gt5688 two more minimal changes piled up so I'm
> folding these in here. One is a doc update for the goodix bindings, the
> other one makes it a bit simpler to figure out configuration problems
> (like lack of touchscreen-size-{x,y} in the device tree.
>
> I've kept the original subject to (hopefully) not break the series for
> patchwork. All patches can be applied independently. Series is based on
> next-20190208.
>
> Changes from v2
> * Add 'dt-bindings: input: Refer to touchscreen.txt for goodix ts'
> * Add 'input: goodix: Print values in case of inconsistencies'
> (sent out separtely before, no comments so far)
> * Collect 'Reviewed-By' on 'input: goodix - support Goodix gt5688'
Applied the lot, thank you.
--
Dmitry
prev parent reply other threads:[~2019-02-17 7:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 14:11 [PATCH v3 0/3] input: goodix - support Goodix gt5688 Guido Günther
2019-02-15 14:11 ` [PATCH v3 1/3] " Guido Günther
2019-02-15 14:11 ` [PATCH v3 2/3] dt-bindings: input: Refer to touchscreen.txt for goodix ts Guido Günther
2019-02-15 14:11 ` [PATCH v3 3/3] input: goodix: Print values in case of inconsistencies Guido Günther
2019-02-17 7:07 ` Dmitry Torokhov [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=20190217070527.GC148958@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=hadess@hadess.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.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).