linux-kernel - Re: [PATCH v4 0/2] ASoC: dt-bindings: Convert TI TWL4030 sound bindings to schema

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: <175572826140.300376.10438251274472224671.b4-ty@kernel.org>
Date: Wed, 20 Aug 2025 23:17:41 +0100
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, robh@...nel.org, 
 Jihed Chaibi <jihed.chaibi.dev@...il.com>
Cc: peter.ujfalusi@...il.com, krzk+dt@...nel.org, conor+dt@...nel.org, 
 devicetree@...r.kernel.org, linux-sound@...r.kernel.org, 
 linux-omap@...r.kernel.org, linux-kernel@...r.kernel.org, shuah@...nel.org
Subject: Re: [PATCH v4 0/2] ASoC: dt-bindings: Convert TI TWL4030 sound
 bindings to schema

On Tue, 19 Aug 2025 22:13:00 +0200, Jihed Chaibi wrote:
> This series converts the legacy TXT bindings for the TI TWL4030
> sound-related modules to the modern YAML DT schema format.
> 
> This work was previously part of a larger series but is now being sent
> as a focused submission for the ASoC subsystem.
> 
> Link to v3 discussion:
> https://lore.kernel.org/all/20250816021523.167049-1-jihed.chaibi.dev@gmail.com/
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: ti,twl4030-audio: convert to DT schema
      commit: 04113322406b4763677922f80ba5ab44a8dae7bb
[2/2] ASoC: dt-bindings: omap-twl4030: convert to DT schema
      commit: c232495d28ca092d0c39b10e35d3d613bd2414ab

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