linux-kernel - Re: [PATCH v1] ASoc: tas2781: Set "Speaker Force Firmware Load" as the common kcontrol for both tas27871 and tas2563

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: <172011485009.96119.17388266064091597967.b4-ty@kernel.org>
Date: Thu, 04 Jul 2024 18:40:50 +0100
From: Mark Brown <broonie@...nel.org>
To: Shenghao Ding <shenghao-ding@...com>
Cc: andriy.shevchenko@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 pierre-louis.bossart@...ux.intel.com, 13916275206@....com, 
 zhourui@...qin.com, alsa-devel@...a-project.org, i-salazar@...com, 
 linux-kernel@...r.kernel.org, j-chadha@...com, liam.r.girdwood@...el.com, 
 jaden-yue@...com, yung-chuan.liao@...ux.intel.com, dipa@...com, 
 yuhsuan@...gle.com, henry.lo@...com, tiwai@...e.de, baojun.xu@...com, 
 soyer@....hu, Baojun.Xu@....com, judyhsiao@...gle.com, navada@...com, 
 cujomalainey@...gle.com, aanya@...com, nayeem.mahmud@...com, 
 savyasanchi.shukla@...radyne.com, flaviopr@...rosoft.com, jesse-ji@...com, 
 darren.ye@...iatek.com
Subject: Re: [PATCH v1] ASoc: tas2781: Set "Speaker Force Firmware Load" as
 the common kcontrol for both tas27871 and tas2563

On Thu, 04 Jul 2024 17:49:37 +0800, Shenghao Ding wrote:
> Set "Speaker Force Firmware Load" as the common kcontrol
> for both tas27871 and tas2563 and move it into newly-created
> tasdevice_snd_controls, and keep the digital gain and analog
> gain in tas2781_snd_controls.
> 
> 

Applied to

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

Thanks!

[1/1] ASoc: tas2781: Set "Speaker Force Firmware Load" as the common kcontrol for both tas27871 and tas2563
      commit: cabf0b0cff07bc8d6e80ab6a8f8a127a2708147b

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