linux-kernel - Re: [PATCH v2 0/2] ASoC: dt-bindings: convert qcom sound bindings to yaml

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <172066024227.393700.11903720765661169490.b4-ty@kernel.org>
Date: Thu, 11 Jul 2024 02:10:42 +0100
From: Mark Brown <broonie@...nel.org>
To: devicetree@...r.kernel.org, Rayyan Ansari <rayyan.ansari@...aro.org>
Cc: alsa-devel@...a-project.org, Banajit Goswami <bgoswami@...cinc.com>, 
 Conor Dooley <conor+dt@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-arm-msm@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-sound@...r.kernel.org, 
 Rob Herring <robh@...nel.org>, 
 Srinivas Kandagatla <srinivas.kandagatla@...aro.org>
Subject: Re: [PATCH v2 0/2] ASoC: dt-bindings: convert qcom sound bindings
 to yaml

On Wed, 10 Jul 2024 12:36:05 +0100, Rayyan Ansari wrote:
> These patches convert the remaining plain text bindings for Qualcomm
> sound drivers to dt schema, so device trees can be validated against
> them.
> 
> v1: https://lore.kernel.org/all/20240709152808.155405-1-rayyan.ansari@linaro.org/
> 
> Thanks,
> Rayyan
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: qcom,msm8916-wcd-digital-codec: convert to dtschema
      commit: 054ac9c97c7d9eb55f471fc6f019b654d17332a7
[2/2] ASoC: dt-bindings: qcom,apq8096-sndcard: use dtschema
      commit: 3cbda25e2db28b4352c73d4167f0dab10049ea54

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