linux-kernel - Re: [PATCH v2 2/2] ASoC: Adds support for TAS575x to the pcm512x driver

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: <169633919804.32637.4231540899734549446.b4-ty@kernel.org>
Date:   Tue, 03 Oct 2023 14:19:58 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Joerg Schambacher <joerg.hifiberry@...il.com>
Cc:     a-krasser@...com, joerg@...iberry.com,
        Liam Girdwood <lgirdwood@...il.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Uwe Kleine-König <u.kleine-koenig@...gutronix.de>,
        Zhang Qilong <zhangqilong3@...wei.com>,
        alsa-devel@...a-project.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/2] ASoC: Adds support for TAS575x to the pcm512x
 driver

On Fri, 29 Sep 2023 17:07:20 +0200, Joerg Schambacher wrote:
> Enables the existing pcm512x driver to control the almost
> compatible TAS5754 and -76 amplifers. Both amplifiers support
> only an I2C interface and the internal PLL must be always
> on to provide necessary clocks to the amplifier section.
> Tested on TAS5756 with support from Andreas Arbesser-Krasser
> from Texas Instruments <a-krasser@...com>
> 
> [...]

Applied to

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

Thanks!

[2/2] ASoC: Adds support for TAS575x to the pcm512x driver
      commit: 1f817805262c2c34142291da376d4932d3c493bc

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