From: Job Noorman <job@noorman.info>
To: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Luca Weiss <luca@z3ntu.xyz>
Subject: Re: [PATCH v2 1/3] dt-bindings: touchscreen: add Himax hx83112b bindings
Date: Fri, 14 Oct 2022 07:24:07 +0000 [thread overview]
Message-ID: <CNLGSQCYFNR1.3HBI9N3N0A77B@ancom> (raw)
In-Reply-To: <166569274210.175113.9615851655183284739.robh@kernel.org>
Hi Rob,
Thanks for you review!
On Thu Oct 13, 2022 at 10:25 PM CEST, Rob Herring wrote:
> On Wed, 12 Oct 2022 20:24:06 +0000, Job Noorman wrote:
> > This patch adds device tree bindings for Himax 83112b touchscreen
> > devices.
> >
> > Signed-off-by: Job Noorman <job@noorman.info>
> > ---
> > .../input/touchscreen/himax,hx83112b.yaml | 61 +++++++++++++++++++
> > MAINTAINERS | 6 ++
> > 2 files changed, 67 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/input/touchscreen/himax,hx83112b.yaml
> >
>
> Reviewed-by: Rob Herring <robh@kernel.org>
The next version of this patch will make the properties touchscreen-size-{x,y}
required. Can I still attach your "Reviewed-by" tag to this updated patch or
would you like to have a look at it first?
Kind regards,
Job
next prev parent reply other threads:[~2022-10-14 7:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 20:23 [PATCH v2 0/3] Add Himax hx83112b touchscreen driver Job Noorman
2022-10-12 20:24 ` [PATCH v2 1/3] dt-bindings: touchscreen: add Himax hx83112b bindings Job Noorman
2022-10-13 20:25 ` Rob Herring
2022-10-14 7:24 ` Job Noorman [this message]
2022-10-12 20:24 ` [PATCH v2 2/3] Input: add driver for Himax hx83112b touchscreen devices Job Noorman
2022-10-13 2:34 ` Jeff LaBundy
2022-10-13 14:57 ` Job Noorman
2022-10-14 1:39 ` Jeff LaBundy
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=CNLGSQCYFNR1.3HBI9N3N0A77B@ancom \
--to=job@noorman.info \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@z3ntu.xyz \
--cc=robh+dt@kernel.org \
--cc=robh@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).