linux-kernel - Re: [PATCH v2 0/2] ASoC: add compatible for ti,pcm5242

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]

Date: Sun, 23 Jun 2024 18:22:05 +0100
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, Rob Herring <robh@...nel.org>, 
 Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Shenghao Ding <shenghao-ding@...com>, 
 Kevin Lu <kevin-lu@...com>, Baojun Xu <baojun.xu@...com>, 
 Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>, 
 linux-sound@...r.kernel.org, devicetree@...r.kernel.org, 
 linux-kernel@...r.kernel.org, alsa-devel@...a-project.org, 
 Christian Hewitt <christianshewitt@...il.com>
Subject: Re: [PATCH v2 0/2] ASoC: add compatible for ti,pcm5242

On Sat, 22 Jun 2024 13:12:43 +0000, Christian Hewitt wrote:
> Update bindings and add a driver compatible for the pcm5242
> chip used on the Odroid HiFi-Shield2 i2c mezzanine board.
> 
> v2 adds a compatible to the SPI variant at Mark's suggestion
> and fixes the binding patch title/description which I managed
> to fat-finger in v1.
> 
> [...]

Applied to

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

Thanks!

[1/2] dt-bindings: sound: add ti,pcm5242 to pcm512x
      commit: 9427997a5e13320a3c404a0cb67a292ad8e00b62
[2/2] ASoC: Add support for ti,pcm5242 to the pcm512x driver
      commit: 9c9b172fdd918c2f852140fc4a3cd827b78fa947

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