[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167328295277.323147.12695338235961954458.b4-ty@kernel.org>
Date: Mon, 09 Jan 2023 16:49:12 +0000
From: Mark Brown <broonie@...nel.org>
To: Srinivas Kandagatla <srinivas.kandagatla@...aro.org>,
Banajit Goswami <bgoswami@...cinc.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
alsa-devel@...a-project.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 1/3] ASoC: dt-bindings: qcom,lpass-cpu: Document required-opps
On Tue, 27 Dec 2022 17:31:33 +0100, Krzysztof Kozlowski wrote:
> SC7280 LPASS CPU device node comes with required-opps:
>
> sc7280-herobrine-crd.dtb: audio@...7000: Unevaluated properties are not allowed ('required-opps' was unexpected)
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: dt-bindings: qcom,lpass-cpu: Document required-opps
commit: a1df78540da20b9ce30a5b24b395d2b4a0f4319e
[2/3] ASoC: dt-bindings: qcom,lpass-cpu: Fix DAI children pattern
commit: 5f9cd0f7c1499174b099a1bda67693df268e711e
[3/3] ASoC: dt-bindings: qcom,lpass-cpu: Correct and constrain clocks, interrupts, reg
commit: ffb2bbdf79d7e712782fd5f44fc250f3e07b3b92
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