devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: AngeloGioacchino Del Regno 
	<angelogioacchino.delregno@somainline.org>,
	linux-input@vger.kernel.org
Cc: konrad.dybcio@somainline.org, marijn.suijten@somainline.org,
	martin.botka@somainline.org, phone-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org, dmitry.torokhov@gmail.com,
	devicetree@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH 0/2] Add support for Goodix GT9286 chip
Date: Sat, 09 Jan 2021 15:37:40 +0100	[thread overview]
Message-ID: <5c923458ee8f86efed2ab1c49906dd89789f663b.camel@hadess.net> (raw)
In-Reply-To: <20210109135512.149032-1-angelogioacchino.delregno@somainline.org>

On Sat, 2021-01-09 at 14:55 +0100, AngeloGioacchino Del Regno wrote:
> Add support for the GT9286 chip, tested on F(x)Tec Pro1 (MSM8998).

Can you please add this test information to the commit message for the
goodix.c patch?

Feel free to add my:
Reviewed-by: Bastien Nocera <hadess@hadess.net>
to both patches when you send a v2.

Cheers

> 
> AngeloGioacchino Del Regno (2):
>   input: goodix: Add support for Goodix GT9286 chip
>   dt-bindings: ts: goodix: Add binding for GT9286 IC
> 
>  Documentation/devicetree/bindings/input/touchscreen/goodix.yaml | 1
> +
>  drivers/input/touchscreen/goodix.c                              | 2
> ++
>  2 files changed, 3 insertions(+)
> 



  parent reply	other threads:[~2021-01-09 14:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-09 13:55 [PATCH 0/2] Add support for Goodix GT9286 chip AngeloGioacchino Del Regno
2021-01-09 13:55 ` [PATCH 1/2] input: goodix: " AngeloGioacchino Del Regno
2021-01-10  6:18   ` Dmitry Torokhov
2021-01-09 13:55 ` [PATCH 2/2] dt-bindings: ts: goodix: Add binding for GT9286 IC AngeloGioacchino Del Regno
2021-01-10  6:18   ` Dmitry Torokhov
2021-01-09 14:37 ` Bastien Nocera [this message]
2021-01-10  6:17   ` [PATCH 0/2] Add support for Goodix GT9286 chip 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=5c923458ee8f86efed2ab1c49906dd89789f663b.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=angelogioacchino.delregno@somainline.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=konrad.dybcio@somainline.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=martin.botka@somainline.org \
    --cc=phone-devel@vger.kernel.org \
    --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).