linux-kernel - Re: [PATCH] ASoC: Intel: soc-acpi-intel-mtl-match: Change CS35L56 prefixes to AMPn

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: <170232142629.117554.17625573039640052470.b4-ty@kernel.org>
Date:   Mon, 11 Dec 2023 19:03:46 +0000
From:   Mark Brown <broonie@...nel.org>
To:     pierre-louis.bossart@...ux.intel.com,
        Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc:     peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
        kai.vehmanen@...ux.intel.com, cezary.rojewski@...el.com,
        ranjani.sridharan@...ux.intel.com, alsa-devel@...a-project.org,
        linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
        patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: Intel: soc-acpi-intel-mtl-match: Change CS35L56
 prefixes to AMPn

On Tue, 05 Dec 2023 11:57:15 +0000, Richard Fitzgerald wrote:
> Change the ALSA prefix for the CS35L56 to "AMPn".
> 
> This keeps them consistent with the CS35L56 HDA driver. It also
> avoids coding the chip ID into the control name, so that other
> Cirrus amps with the same controls can have the same control
> names.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: soc-acpi-intel-mtl-match: Change CS35L56 prefixes to AMPn
      commit: 02a914ed475dd928c7b2b6c9d1da9b0b27fa724d

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