mbox series

[v3,0/2] Update lpass dt-bindings

Message ID 1674468802-14834-1-git-send-email-quic_srivasam@quicinc.com (mailing list archive)
Headers show
Series Update lpass dt-bindings | expand

Message

Srinivasa Rao Mandadapu Jan. 23, 2023, 10:13 a.m. UTC
Update va-macro driver dt-bindings and add missing properties in sc7280 
machine driver dt-bindings.

Changes since v2:
    -- Update commit message and example in "Add platform property" patch.
    -- Update commit message in "Update clock name" patch.
Changes since v1:
    -- Remove sound-dai cells property patch.
    -- Update example in clock name change patch.
    -- Update commit message and add maxItems in platform proerty patch.

Srinivasa Rao Mandadapu (2):
  ASoC: qcom: dt-bindings: lpass-va-macro: Update clock name
  ASoC: dt-bindings: google,sc7280-herobrine: Add platform property

 .../devicetree/bindings/sound/google,sc7280-herobrine.yaml   | 12 ++++++++++++
 .../devicetree/bindings/sound/qcom,lpass-va-macro.yaml       |  4 ++--
 2 files changed, 14 insertions(+), 2 deletions(-)

Comments

Mark Brown Jan. 26, 2023, 5:09 p.m. UTC | #1
On Mon, 23 Jan 2023 15:43:20 +0530, Srinivasa Rao Mandadapu wrote:
> Update va-macro driver dt-bindings and add missing properties in sc7280
> machine driver dt-bindings.
> 
> Changes since v2:
>     -- Update commit message and example in "Add platform property" patch.
>     -- Update commit message in "Update clock name" patch.
> Changes since v1:
>     -- Remove sound-dai cells property patch.
>     -- Update example in clock name change patch.
>     -- Update commit message and add maxItems in platform proerty patch.
> 
> [...]

Applied to

   broonie/sound.git for-next

Thanks!

[1/2] ASoC: qcom: dt-bindings: lpass-va-macro: Update clock name
      commit: 7a35498982e84e4d39e8c259f251dfa588f0f039
[2/2] ASoC: dt-bindings: google,sc7280-herobrine: Add platform property
      commit: ec9009724027b6599ee79a8ac6c97de442ad6f6d

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