From: Adam Ford <aford173@gmail.com>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Marek Vasut <marex@denx.de>,
linux-input@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] Input: ili210x - add ILI2117 support
Date: Tue, 5 Nov 2019 07:27:15 -0600 [thread overview]
Message-ID: <CAHCN7xJ501UHTRRi-fdi7cFH_Bhz07hpa9wRaP1D0MGWrDmbkQ@mail.gmail.com> (raw)
In-Reply-To: <CAGngYiX1JP8NZBU+wRzdsLBMN7hhsbmfaD5o4PGPX27Q-6J4xw@mail.gmail.com>
On Mon, Nov 4, 2019 at 8:04 PM Sven Van Asbroeck <thesven73@gmail.com> wrote:
>
> On Mon, Nov 4, 2019 at 6:40 PM Adam Ford <aford173@gmail.com> wrote:
> >
> > I will test it tomorrow on a 2117a and reply with results. I am very
> > excited to see this integrated.
For the series: Tested-by: Adam Ford <aford173@gmail.com> #imx6q-logicpd
adam
> >
>
> I will do the same. That should give us confidence that 211x works
> ok.
>
> Dmitry, should someone retest 251x and 210x after such a significant
> change? Unfortunately I don't have access to these chips.
next prev parent reply other threads:[~2019-11-05 13:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190302141704.32547-1-marex@denx.de>
2019-11-01 20:48 ` [PATCH 2/2] Input: ili210x - add ILI2117 support Sven Van Asbroeck
2019-11-03 23:55 ` Adam Ford
2019-11-04 0:16 ` Marek Vasut
2019-11-04 7:02 ` Dmitry Torokhov
2019-11-04 7:01 ` Dmitry Torokhov
2019-11-04 9:13 ` Marek Vasut
2019-11-04 13:49 ` Sven Van Asbroeck
2019-11-04 14:19 ` Adam Ford
2019-11-04 18:36 ` Dmitry Torokhov
2019-11-04 18:37 ` Sven Van Asbroeck
2019-11-04 21:28 ` Adam Ford
2019-11-04 21:43 ` Sven Van Asbroeck
2019-11-04 23:25 ` Adam Ford
2019-11-04 23:36 ` Dmitry Torokhov
2019-11-04 23:40 ` Adam Ford
2019-11-05 2:04 ` Sven Van Asbroeck
2019-11-05 13:27 ` Adam Ford [this message]
2019-11-05 15:26 ` Sven Van Asbroeck
2019-11-05 15:29 ` Sven Van Asbroeck
2019-11-05 15:53 ` Sven Van Asbroeck
2019-11-11 18:16 ` Dmitry Torokhov
2019-11-11 18:43 ` Rob Herring
2019-11-12 0:19 ` 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=CAHCN7xJ501UHTRRi-fdi7cFH_Bhz07hpa9wRaP1D0MGWrDmbkQ@mail.gmail.com \
--to=aford173@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marex@denx.de \
--cc=thesven73@gmail.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).