[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <175268140929.726552.6903010373670247326.b4-ty@kernel.org>
Date: Wed, 16 Jul 2025 16:56:49 +0100
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srini@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-sound@...r.kernel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Subject: Re: [PATCH] ASoC: dt-bindings: qcom,lpass-va-macro: Define
clock-names in top-level
On Wed, 16 Jul 2025 09:49:58 +0200, Krzysztof Kozlowski wrote:
> Device variants use different amount of clock inputs, but all of them
> are in the same order, 'clock-names' in top-level properties can define
> the list and each if:then: block can only narrow the number of items.
>
> This is preferred syntax, because it keeps list unified among devices
> and encourages adding new entries to the end of the list, instead of
> adding them in the middle. The change has no functional impact, but
> partially reverts approach implemented in commit cfad817095e1 ("ASoC:
> dt-bindings: qcom,lpass-va-macro: Add missing NPL clock").
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: dt-bindings: qcom,lpass-va-macro: Define clock-names in top-level
commit: aa84580e058c4d7567b2a5e5a9d12f94af75d297
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
Powered by blists - more mailing lists