From: Krzysztof Kozlowski <krzk@kernel.org>
To: webgeek1234@gmail.com, 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>
Cc: devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] arm64: tegra: Add CPU OPP tables for Tegra186/Tegra194
Date: Tue, 21 Oct 2025 22:08:19 +0200 [thread overview]
Message-ID: <9c1f79b2-d118-452e-8e75-d1156ade430f@kernel.org> (raw)
In-Reply-To: <20251021-tegra186-icc-p3-v1-0-0c313968b77b@gmail.com>
On 21/10/2025 20:31, Aaron Kling via B4 Relay wrote:
> This was original part of a larger series [0], but it was requested to
> be split into smaller series.
>
> [0] https://lore.kernel.org/r/20250909-tegra186-icc-v2-0-09413724e781@gmail.com
>
> Signed-off-by: Aaron Kling <webgeek1234@gmail.com>
> ---
> Aaron Kling (2):
> arm64: tegra: Add CPU OPP tables for Tegra186
> arm64: tegra: Add CPU OPP tables for Tegra194
>
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 317 +++++++++++++++
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 636 +++++++++++++++++++++++++++++++
> 2 files changed, 953 insertions(+)
> ---
> base-commit: 211ddde0823f1442e4ad052a2f30f050145ccada
> change-id: 20251021-tegra186-icc-p3-3f6454da5ec4
> prerequisite-change-id: 20251021-tegra186-icc-p1-8455e61d453d:v1
> prerequisite-patch-id: 79b5490cea531a49046c96e8b5240dbbe490e16a
> prerequisite-change-id: 20251021-tegra186-icc-p2-864fd8625699:v1
> prerequisite-patch-id: 470c94ee34569e507d14e65dd989e708955f1512
> prerequisite-patch-id: 64f466efb923428edb27b4360ac41bda5c990311
> prerequisite-patch-id: 6a99ee6dbcae73fcbfab52009fd600b2618f3d5a
> prerequisite-patch-id: e05146355f318629f1511fa972c1b1f92ee98064
> prerequisite-patch-id: 5754b9afa57bdf187d8779a3354fdbc36e539af9
You really did not want to follow my advice, right? I said nothing about
b4 deps, because above cannot be true. Your DTS cannot depend on driver
patches.
This patchset is now wrong. Please read my advice one more time, I wrote
it very detailed.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-21 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 18:31 Aaron Kling via B4 Relay
2025-10-21 18:31 ` [PATCH 1/2] arm64: tegra: Add CPU OPP tables for Tegra186 Aaron Kling via B4 Relay
2025-10-21 18:31 ` [PATCH 2/2] arm64: tegra: Add CPU OPP tables for Tegra194 Aaron Kling via B4 Relay
2025-10-21 20:08 ` 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=9c1f79b2-d118-452e-8e75-d1156ade430f@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=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
all inboxes | Powered by JetHome®