Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: devicetree@vger.kernel.org,
	 Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: 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>,
	 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: Re: (subset) [PATCH 0/4] dt-bindings: treewide: don't check node names
Date: Fri, 24 Oct 2025 11:24:04 +0100	[thread overview]
Message-ID: <176130144489.10577.5538260652511597774.b4-ty@kernel.org> (raw)
In-Reply-To: <20251020060951.30776-6-wsa+renesas@sang-engineering.com>

On Mon, 20 Oct 2025 08:09:49 +0200, Wolfram Sang wrote:
> 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.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[4/4] dt-bindings: spi: don't check node names
      commit: 7c69694cec869e3bf7c810fd94f860253aeb8053

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


  parent reply	other threads:[~2025-10-24 10:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  6:09 [PATCH 0/4] dt-bindings: treewide: don't check node names Wolfram Sang
2025-10-20  6:09 ` [PATCH 3/4] ASoC: dt-bindings: " 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 [this message]
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=176130144489.10577.5538260652511597774.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --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 \
    --cc=wsa+renesas@sang-engineering.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