From: Mikko Perttunen <mperttunen@nvidia.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
webgeek1234@gmail.com
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Aaron Kling <webgeek1234@gmail.com>
Subject: Re: [PATCH v3 3/3] arm64: tegra: Add Tegra186 pin controllers
Date: Wed, 03 Sep 2025 13:06:38 +0900 [thread overview]
Message-ID: <5247140.MHq7AAxBmi@senjougahara> (raw)
In-Reply-To: <20250812-tegra186-pinctrl-v3-3-115714eeecb1@gmail.com>
On Wednesday, August 13, 2025 6:24 AM Aaron Kling via B4 Relay wrote:
> From: Aaron Kling <webgeek1234@gmail.com>
>
> Add the device tree nodes for the MAIN and AON pin controllers found on
> the Tegra186 family of SoCs.
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 12 ++
> drivers/pinctrl/tegra/pinctrl-tegra186.c | 207 ++++++++++++++++++++++++++++++-
The whitespace changes seem to have ended up in this patch. Please separate them out.
Thanks,
Mikko
next prev parent reply other threads:[~2025-09-03 4:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 21:24 [PATCH v3 0/3] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 1/3] dt-bindings: pinctrl: Document Tegra186 pin controllers Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 2/3] pinctrl: tegra: Add Tegra186 pinmux driver Aaron Kling via B4 Relay
2025-08-12 21:24 ` [PATCH v3 3/3] arm64: tegra: Add Tegra186 pin controllers Aaron Kling via B4 Relay
2025-09-03 4:06 ` Mikko Perttunen [this message]
2025-10-16 15:16 ` Thierry Reding
2025-08-19 11:29 ` [PATCH v3 0/3] pinctrl: tegra: Add Tegra186 pinmux driver Linus Walleij
2025-09-03 4:53 ` Aaron Kling
2025-09-03 6:55 ` Linus Walleij
2025-09-03 17:58 ` Aaron Kling
2025-09-04 13:09 ` Thierry Reding
2025-10-14 17:54 ` Aaron Kling
2025-10-16 22:17 ` Linus Walleij
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=5247140.MHq7AAxBmi@senjougahara \
--to=mperttunen@nvidia.com \
--cc=brgl@bgdev.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--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