Re: (subset) [PATCH v4 00/15] ASoC/qcom/arm64: Qualcomm ADSP DTS and binding fixes

From: Mark Brown
Date: Thu Sep 15 2022 - 05:31:28 EST


On Sat, 10 Sep 2022 11:14:13 +0200, Krzysztof Kozlowski wrote:
> Dependencies/merging
> ====================
> 1. The DTS patches are independent.
> 2. The binding patches should come together, because of context changes. Could
> be one of: Qualcomm SoC, ASoC or DT tree.
>
> Changes since v3
> ================
> 1. Patch 9-10: re-order, so first apr.yaml is corrected and then we convert to
> DT schema. This makes patchset fully bisectable in expense of changing the same
> lines twice.
> 2. Patch 11: New patch.
>
> [...]

Applied to

broonie/sound.git for-next

Thanks!

[09/15] dt-bindings: soc: qcom: apr: correct service children
commit: b2496de1dfdddfceb87e7a7b791c3a249c860682
[10/15] ASoC: dt-bindings: qcom,q6asm: convert to dtschema
commit: 7b0ad4629d1fb719ae71a8f2968e8c6268ab1709
[11/15] ASoC: dt-bindings: qcom,q6adm: convert to dtschema
commit: 301628d805019999f1ae9764aadfcface9c4e309
[12/15] ASoC: dt-bindings: qcom,q6dsp-lpass-ports: cleanup example
commit: 0630efc3b849f65ef3bad803b84bc0819591dac9
[13/15] ASoC: dt-bindings: qcom,q6dsp-lpass-clocks: cleanup example
commit: 7af18f4efd85c2e85458e3f504e129a97f6baaf2
[14/15] ASoC: dt-bindings: qcom,q6apm-dai: adjust indentation in example
commit: 5f170e21fe96fbd1f81ace9ec6e6b695e1098733
[15/15] dt-bindings: soc: qcom: apr: add missing properties
commit: b2d7616e13c4eb766f5e2f6568c2e746e76b7b53

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