From: Krzysztof Kozlowski <krzk@kernel.org>
To: pshete@nvidia.com, linusw@kernel.org, thierry.reding@kernel.org
Cc: jonathanh@nvidia.com, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, webgeek1234@gmail.com, rosenp@gmail.com,
linux-tegra@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers
Date: Tue, 21 Apr 2026 11:53:16 +0200 [thread overview]
Message-ID: <39b81e8d-0c0e-4b6d-b77e-274d631f26c8@kernel.org> (raw)
In-Reply-To: <20260420100601.343707-5-pshete@nvidia.com>
On 20/04/2026 12:05, pshete@nvidia.com wrote:
> From: Prathamesh Shete <pshete@nvidia.com>
>
> Tegra264 contains three pin controllers. Document their
> compatible strings and describe the list of pins and
> functions that they provide.
Same comment about commit msg.
I cannot compare with previous version, because you broke it with this
style of posting. Please do not use non-standard way of posting things.
b4 is there for you on purpose, so when you do not know how to do it,
the tool does it for you.
With commit msg fixed:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-21 9:53 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 13:13 [PATCH 0/6] Add Tegra238 and Tegra264 pinctrl support pshete
2026-04-09 13:13 ` [PATCH 1/6] pinctrl: tegra: Export tegra_pinctrl_probe() pshete
2026-04-09 13:13 ` [PATCH 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers pshete
2026-04-10 11:00 ` Krzysztof Kozlowski
2026-04-10 11:04 ` Krzysztof Kozlowski
2026-04-09 13:13 ` [PATCH 3/6] pinctrl: tegra: Add Tegra238 pinmux driver pshete
2026-04-10 10:05 ` Krzysztof Kozlowski
2026-04-09 13:13 ` [PATCH 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers pshete
2026-04-09 13:13 ` [PATCH 5/6] pinctrl: tegra: Add Tegra264 pinmux driver pshete
2026-04-09 13:13 ` [PATCH 6/6] arm64: defconfig: make Tegra238 and Tegra264 Pinctrl a loadable module pshete
2026-04-10 6:37 ` Krzysztof Kozlowski
2026-04-10 8:25 ` Jon Hunter
2026-04-13 9:49 ` Jon Hunter
2026-04-16 14:30 ` Thierry Reding
2026-04-16 14:37 ` Krzysztof Kozlowski
2026-04-20 10:05 ` [PATCH v2 0/6] Add Tegra238 and Tegra264 pinctrl support pshete
2026-04-20 10:05 ` [PATCH v2 1/6] pinctrl: tegra: Export tegra_pinctrl_probe() pshete
2026-04-20 10:05 ` [PATCH v2 2/6] dt-bindings: pinctrl: Document Tegra238 pin controllers pshete
2026-04-21 8:31 ` Krzysztof Kozlowski
2026-04-21 8:37 ` Krzysztof Kozlowski
2026-04-21 9:32 ` Thierry Reding
2026-04-20 10:05 ` [PATCH v2 3/6] pinctrl: tegra: Add Tegra238 pinmux driver pshete
2026-04-20 10:05 ` [PATCH v2 4/6] dt-bindings: pinctrl: Document Tegra264 pin controllers pshete
2026-04-21 9:53 ` Krzysztof Kozlowski [this message]
2026-04-20 10:06 ` [PATCH v2 5/6] pinctrl: tegra: Add Tegra264 pinmux driver pshete
2026-04-20 10:06 ` [PATCH] arm64: tegra: Add pinctrl nodes for Tegra264 pshete
2026-04-21 8:27 ` Krzysztof Kozlowski
2026-04-21 9:53 ` Jon Hunter
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=39b81e8d-0c0e-4b6d-b77e-274d631f26c8@kernel.org \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=pshete@nvidia.com \
--cc=robh@kernel.org \
--cc=rosenp@gmail.com \
--cc=thierry.reding@kernel.org \
--cc=webgeek1234@gmail.com \
/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