From: Rob Herring <robh@kernel.org>
To: Markuss Broks <markuss.broks@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
Henrik Rydberg <rydberg@bitmath.org>,
~postmarketos/upstreaming@lists.sr.ht,
linux-input@vger.kernel.org,
Stephen Rothwell <sfr@canb.auug.org.au>,
phone-devel@vger.kernel.org, devicetree@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Subject: Re: [PATCH v6 1/2] dt-bindings: input/touchscreen: bindings for Imagis
Date: Wed, 23 Feb 2022 09:57:57 -0600 [thread overview]
Message-ID: <YhZZhUVldKkSaKsb@robh.at.kernel.org> (raw)
In-Reply-To: <20220222203414.8656-2-markuss.broks@gmail.com>
On Tue, 22 Feb 2022 22:34:10 +0200, Markuss Broks wrote:
> This patch adds device-tree bindings for the Imagis
> IST3038C touch screen IC.
>
> Signed-off-by: Markuss Broks <markuss.broks@gmail.com>
>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
> ---
> .../input/touchscreen/imagis,ist3038c.yaml | 74 +++++++++++++++++++
> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
> 2 files changed, 76 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/input/touchscreen/imagis,ist3038c.yaml
>
Acked-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-02-23 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 20:34 [PATCH v6 0/2] Add support for Imagis touchscreens Markuss Broks
2022-02-22 20:34 ` [PATCH v6 1/2] dt-bindings: input/touchscreen: bindings for Imagis Markuss Broks
2022-02-23 8:07 ` Krzysztof Kozlowski
2022-02-23 15:57 ` Rob Herring [this message]
2022-02-22 20:34 ` [PATCH v6 2/2] Input: add Imagis touchscreen driver Markuss Broks
2022-02-23 4:59 ` kernel test robot
2022-02-23 15:41 ` kernel test robot
2022-02-25 7:55 ` Dan Carpenter
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=YhZZhUVldKkSaKsb@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markuss.broks@gmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=rydberg@bitmath.org \
--cc=sfr@canb.auug.org.au \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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).