From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: devicetree@vger.kernel.org
Cc: Wolfram Sang <wsa+renesas@sang-engineering.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Chen-Yu Tsai <wens@csie.org>, Conor Dooley <conor+dt@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
Fabrice Gasnier <fabrice.gasnier@foss.st.com>,
Gatien Chevallier <gatien.chevallier@foss.st.com>,
imx@lists.linux.dev, Jernej Skrabec <jernej.skrabec@gmail.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, linux-sound@vger.kernel.org,
linux-spi@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-sunxi@lists.linux.dev, Liu Ying <victor.liu@nxp.com>,
Mark Brown <broonie@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Samuel Holland <samuel@sholland.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Srinivas Kandagatla <srini@kernel.org>
Subject: [PATCH 0/4] dt-bindings: treewide: don't check node names
Date: Mon, 20 Oct 2025 08:09:49 +0200 [thread overview]
Message-ID: <20251020060951.30776-6-wsa+renesas@sang-engineering.com> (raw)
Node names are already and properly checked by the core schema. No need
to do it again.
These are all occurrences I found in linux-next as of 20251015. I did
run dt_bindings_check successfully. I haven't done a way to run
dtbs_check yet because I would need to identify the proper architecture
first, right? Is there some tool which tests all DTs of a certain
binding? At least build bot is happy, I don't know if it checks DTs as
well, though.
I'd suggest to give subsystems some time to pick these patches before
Rob applies the remaining ones?
Wolfram Sang (4):
dt-bindings: bus: don't check node names
dt-bindings: nvmem: don't check node names
ASoC: dt-bindings: don't check node names
dt-bindings: spi: don't check node names
.../devicetree/bindings/bus/allwinner,sun8i-a23-rsb.yaml | 2 +-
.../devicetree/bindings/bus/fsl,imx8qxp-pixel-link-msi-bus.yaml | 2 +-
Documentation/devicetree/bindings/bus/st,stm32-etzpc.yaml | 2 +-
Documentation/devicetree/bindings/bus/st,stm32mp25-rifsc.yaml | 2 +-
Documentation/devicetree/bindings/nvmem/st,stm32-romem.yaml | 2 +-
Documentation/devicetree/bindings/sound/qcom,wcd934x.yaml | 2 +-
Documentation/devicetree/bindings/spi/snps,dw-apb-ssi.yaml | 2 +-
Documentation/devicetree/bindings/spi/spi-controller.yaml | 2 +-
8 files changed, 8 insertions(+), 8 deletions(-)
--
2.47.2
next reply other threads:[~2025-10-20 6:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 6:09 Wolfram Sang [this message]
2025-10-20 6:09 ` [PATCH 4/4] dt-bindings: spi: don't check node names Wolfram Sang
2025-10-20 17:58 ` [PATCH 0/4] dt-bindings: treewide: " Conor Dooley
2025-10-21 18:52 ` (subset) " Mark Brown
2025-10-24 10:24 ` Mark Brown
2025-11-10 7:41 ` Srinivas Kandagatla
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=20251020060951.30776-6-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=alexandre.torgue@foss.st.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=fabrice.gasnier@foss.st.com \
--cc=festevam@gmail.com \
--cc=gatien.chevallier@foss.st.com \
--cc=imx@lists.linux.dev \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-sunxi@lists.linux.dev \
--cc=mcoquelin.stm32@gmail.com \
--cc=mripard@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=samuel@sholland.org \
--cc=shawnguo@kernel.org \
--cc=srini@kernel.org \
--cc=victor.liu@nxp.com \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).