From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Felix Kaechele <felix@kaechele.ca>
Cc: Job Noorman <job@noorman.info>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-input@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/5] himax_hx83112b: add support for HX83100A
Date: Mon, 8 Jul 2024 16:16:32 -0700 [thread overview]
Message-ID: <ZoxzUHsGcgYrRXjT@google.com> (raw)
In-Reply-To: <20240620145019.156187-1-felix@kaechele.ca>
On Thu, Jun 20, 2024 at 10:50:01AM -0400, Felix Kaechele wrote:
> Original discussion around v2 here: https://lore.kernel.org/all/20240511121245.109644-1-felix@kaechele.ca/
>
> Changes from v2:
> - reworded dt-bindings commit message to specifiy how the HX83100A is different
> from other chips in this series to justify having its own compatible string
> - added Acked-By from Conor that was given in the v2 thread to commit message
>
> I've done some more testing in the meantime and haven't found any issues.
> I haven't heard back from anyone with an HX83112B, but the HX83100A works as
> intended with these changes and I assume the HX83112B will too.
Applied the lot, thank you.
--
Dmitry
prev parent reply other threads:[~2024-07-08 23:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 14:50 [PATCH v3 0/5] himax_hx83112b: add support for HX83100A Felix Kaechele
2024-06-20 14:50 ` [PATCH v3 1/5] dt-bindings: input: touchscreen: himax,hx83112b: add HX83100A Felix Kaechele
2024-06-20 14:50 ` [PATCH v3 2/5] input: himax_hx83112b: use more descriptive register defines Felix Kaechele
2024-06-20 14:50 ` [PATCH v3 3/5] input: himax_hx83112b: implement MCU register reading Felix Kaechele
2024-06-20 14:50 ` [PATCH v3 4/5] input: himax_hx83112b: add himax_chip struct for multi-chip support Felix Kaechele
2024-06-20 14:50 ` [PATCH v3 5/5] input: himax_hx83112b: add support for HX83100A Felix Kaechele
2024-07-08 23:16 ` Dmitry Torokhov [this message]
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=ZoxzUHsGcgYrRXjT@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=felix@kaechele.ca \
--cc=job@noorman.info \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).