From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jan Remmet <j.remmet@phytec.de>
Cc: "Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Levente Révész" <levente.revesz@eilabs.com>,
linux-gpio@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
upstream@lists.phytec.de
Subject: Re: [PATCH 3/3] dt-bindings: gpio: gpio-pca95xx: Add tcal6408 and tcal6416
Date: Tue, 16 Dec 2025 07:33:13 +0100 [thread overview]
Message-ID: <20251216-happy-beige-bug-a8fad0@quoll> (raw)
In-Reply-To: <20251212-wip-jremmet-tcal6416rtw-v1-3-e5db1b66d4cc@phytec.de>
On Fri, Dec 12, 2025 at 02:03:18PM +0100, Jan Remmet wrote:
> TCAL6408 and TCAL6416 supports latchable inputs and maskable interrupt.
> add compatibles ti,tcal6408 and ti,tcal6416
And are not compatible with other variants? Explain here why.
>
> Signed-off-by: Jan Remmet <j.remmet@phytec.de>
> ---
> Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml | 2 ++
> 1 file changed, 2 insertions(+)
>
Please organize the patch documenting the compatible (DT bindings) before the patch using that compatible.
See also: https://elixir.bootlin.com/linux/v6.14-rc6/source/Documentation/devicetree/bindings/submitting-patches.rst#L46
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
prev parent reply other threads:[~2025-12-16 6:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 13:03 [PATCH 0/3] gpio: pca953x: Add support for TCAL6408 TCAL6416 Jan Remmet
2025-12-12 13:03 ` [PATCH 1/3] " Jan Remmet
2025-12-12 13:03 ` [PATCH 2/3] Documentation: gpio: add TCAL6408 and TCAL6416 Jan Remmet
2025-12-12 13:03 ` [PATCH 3/3] dt-bindings: gpio: gpio-pca95xx: Add tcal6408 and tcal6416 Jan Remmet
2025-12-16 6:33 ` Krzysztof Kozlowski [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=20251216-happy-beige-bug-a8fad0@quoll \
--to=krzk@kernel.org \
--cc=brgl@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=j.remmet@phytec.de \
--cc=krzk+dt@kernel.org \
--cc=levente.revesz@eilabs.com \
--cc=linusw@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=upstream@lists.phytec.de \
/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).