From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jon Hunter <jonathanh@nvidia.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 00/10] dt-bindings: Various cleanups for Tegra-related bindings
Date: Mon, 23 Feb 2026 11:11:40 -0600 [thread overview]
Message-ID: <20260223171140.GA3992907-robh@kernel.org> (raw)
In-Reply-To: <20260223143305.3771383-1-thierry.reding@kernel.org>
On Mon, Feb 23, 2026 at 03:32:55PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> This patch set contains a couple of cleanups and conversions for Tegra-
> related bindings. In total, on top of next-20260220, these patches get
> the number of DT validation issues down from 184 to just 88.
Great! Really, you were at only 40 unique warnings (I strip the
filenames to avoid multiple boards duplicating warnings). You're in 4th
(to last) place:
arch/arm64/boot/dts/hisilicon:116:74
arch/arm64/boot/dts/mediatek:197:48
arch/arm64/boot/dts/qcom:132:45
arch/arm64/boot/dts/nvidia:184:40
arch/arm64/boot/dts/rockchip:76:27
arch/arm64/boot/dts/marvell:182:23
arch/arm64/boot/dts/renesas:83:13
arch/arm64/boot/dts/xilinx:16:6
arch/arm64/boot/dts/microchip:22:6
arch/arm64/boot/dts/broadcom:32:4
arch/arm64/boot/dts/nuvoton:3:3
arch/arm64/boot/dts/sprd:2:2
arch/arm64/boot/dts/intel:2:2
arch/arm64/boot/dts/apm:3:2
arch/arm64/boot/dts/realtek:45:1
arch/arm64/boot/dts/freescale:2:1
arch/arm64/boot/dts/arm:1:1
This and logs of all the warnings from next and Linus' trees can be
retrieved with scripts here:
https://gitlab.com/robherring/ci-jobs
> Note that technically these are at different revisions because they had
> been sent out separately a while ago, Some of these have already been
> reviewed, but given that they are fairly old I wanted to send them out
> in case there are new best practices that these don't include. I've run
> all of these through dt_binding_check. Also I've verified that these do
> not produce any new warnings/errors while eliminating old ones.
>
> Krzysztof, Rob, I know that you prefer DT binding changes to go through
> driver trees, but given that these don't have any driver changes to go
> with them, should we queue these via the Tegra tree (or devicetree tree)
> once they've passed review?
I prefer they go via subsystem trees still, but if you don't get a reply
in reasonable time just take them. You can take the interrupt-controller
one though as DT only changes don't tend to get picked up.
> I plan to pick up the two DTS changes into the Tegra tree since they are
> fairly trivial and unrelated to the bindings changes. I suppose they
> could've just been a separate series, but I thought I'd post them along
> with the other changes since this is all a concerted effort to get the
> number of issues down.
>
> Thanks,
> Thierry
>
> Thierry Reding (10):
> dt-bindings: phy: tegra-xusb: Document Type C support
> dt-bindings: pci: tegra: Convert to json-schema
> dt-bindings: clock: tegra124-dfll: Convert to json-schema
> dt-bindings: interrupt-controller: tegra: Fix reg entries
> dt-bindings: arm: tegra: Add missing compatible strings
> dt-bindings: phy: tegra: Document Tegra210 USB PHY
> dt-bindings: memory: Add Tegra210 memory controller bindings
> dt-bindings: memory: tegra210: Mark EMC as cooling device
> arm64: tegra: Fix snps,blen properties
> arm64: tegra: Drop redundant clock and reset names for TSEC
arm64: dts: tegra: ...
Rob
next prev parent reply other threads:[~2026-02-23 17:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 14:32 [PATCH 00/10] dt-bindings: Various cleanups for Tegra-related bindings Thierry Reding
2026-02-23 14:32 ` [PATCH v2 01/10] dt-bindings: phy: tegra-xusb: Document Type C support Thierry Reding
2026-03-06 0:02 ` Rob Herring (Arm)
2026-02-23 14:32 ` [PATCH 02/10] dt-bindings: pci: tegra: Convert to json-schema Thierry Reding
2026-03-06 0:19 ` Rob Herring
2026-02-23 14:32 ` [PATCH v3 03/10] dt-bindings: clock: tegra124-dfll: " Thierry Reding
2026-03-06 0:22 ` Rob Herring (Arm)
2026-02-23 14:32 ` [PATCH 04/10] dt-bindings: interrupt-controller: tegra: Fix reg entries Thierry Reding
2026-03-06 0:23 ` Rob Herring (Arm)
2026-02-23 14:33 ` [PATCH v2 05/10] dt-bindings: arm: tegra: Add missing compatible strings Thierry Reding
2026-02-23 14:33 ` [PATCH 06/10] dt-bindings: phy: tegra: Document Tegra210 USB PHY Thierry Reding
2026-03-06 0:23 ` Rob Herring (Arm)
2026-02-23 14:33 ` [PATCH v2 07/10] dt-bindings: memory: Add Tegra210 memory controller bindings Thierry Reding
2026-03-06 0:25 ` Rob Herring
2026-02-23 14:33 ` [PATCH 08/10] dt-bindings: memory: tegra210: Mark EMC as cooling device Thierry Reding
2026-02-23 14:33 ` [PATCH 09/10] arm64: tegra: Fix snps,blen properties Thierry Reding
2026-02-23 14:33 ` [PATCH 10/10] arm64: tegra: Drop redundant clock and reset names for TSEC Thierry Reding
2026-02-23 17:11 ` Rob Herring [this message]
2026-02-27 12:03 ` [PATCH 00/10] dt-bindings: Various cleanups for Tegra-related bindings Thierry Reding
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=20260223171140.GA3992907-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@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