From: "'dmitry.torokhov@gmail.com'" <dmitry.torokhov@gmail.com>
To: Matthias Fend <Matthias.Fend@wolfvision.net>
Cc: Martin Kepplinger <martin.kepplinger@ginzinger.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/2] Input: st1232 - handle common DT bindings
Date: Mon, 11 Feb 2019 00:45:02 -0800 [thread overview]
Message-ID: <20190211084502.GC95126@dtor-ws> (raw)
In-Reply-To: <VI1PR08MB37589A1C275E8D0A1224037B85640@VI1PR08MB3758.eurprd08.prod.outlook.com>
Hi Matthias,
On Mon, Feb 11, 2019 at 07:15:12AM +0000, Matthias Fend wrote:
> Hi Dmitry,
>
> You asked me if I could also include the conversion to touchscreen_report_pos() - which I did in this patch version.
> Is there anything else missing?
Sorry, gmail decided to mark the v2 patches as spam for some reason :(
I fished them out and applied.
Matthias, Martin, I noticed that the driver is still using MT-A
protocol. Could you convert it to the proper MT-B (slotted) protocol?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2019-02-11 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1548757144-2222-1-git-send-email-matthias.fend@wolfvision.net>
[not found] ` <1548757144-2222-2-git-send-email-matthias.fend@wolfvision.net>
2019-02-11 7:15 ` AW: [PATCH 2/2] Input: st1232 - handle common DT bindings Matthias Fend
2019-02-11 8:45 ` 'dmitry.torokhov@gmail.com' [this message]
2019-02-11 8:51 ` Martin Kepplinger
2019-02-11 22:21 ` 'dmitry.torokhov@gmail.com'
2019-01-28 9:06 [PATCH 1/2] dt-bindings: input: touchscreen: st1232i: reference " Matthias Fend
[not found] ` <419160a7-edf5-48cf-85ea-d6d5e9cd6e59.95bf7d06-047e-438c-8c7b-895af195351a.6448af99-cd65-4518-8f79-5ccc17d038ab@emailsignatures365.codetwo.com>
2019-01-28 9:06 ` [PATCH 2/2] Input: st1232 - handle " Matthias Fend
2019-01-28 19:08 ` dmitry.torokhov
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=20190211084502.GC95126@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=Matthias.Fend@wolfvision.net \
--cc=devicetree@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=martin.kepplinger@ginzinger.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).