linux-kernel - Re: [PATCH] ASoC: amd: acp: don't set card long

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: <172665845809.1795214.7985418215228293070.b4-ty@kernel.org>
Date: Wed, 18 Sep 2024 13:20:58 +0200
From: Mark Brown <broonie@...nel.org>
To: Vijendar Mukunda <Vijendar.Mukunda@....com>
Cc: alsa-devel@...a-project.org, pierre-louis.bossart@...ux.intel.com, 
 yung-chuan.liao@...ux.intel.com, lgirdwood@...il.com, perex@...ex.cz, 
 tiwai@...e.com, Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com, 
 venkataprasad.potturu@....com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: amd: acp: don't set card long_name

On Mon, 16 Sep 2024 11:43:18 +0530, Vijendar Mukunda wrote:
> UCM can load a board-specific file based on the card long_name. Remove
> the constant "AMD Soundwire SOF" long_name so that the ASoC core can
> set the long_name based on DMI information.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: don't set card long_name
      commit: 8451a3c7879d8883fd3fbd9dd7cbe7ecc31e89ce

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