linux-kernel - Re: [PATCH v3] ASoC: soc-core.c: Prefer to return dai->driver->name in snd_soc_dai_name

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: Tue, 05 Mar 2024 20:41:58 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 kuninori.morimoto.gx@...esas.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, alsa-devel@...a-project.org, 
 Chancel Liu <chancel.liu@....com>
Subject: Re: [PATCH v3] ASoC: soc-core.c: Prefer to return
 dai->driver->name in snd_soc_dai_name_get()

On Mon, 04 Mar 2024 16:21:28 +0900, Chancel Liu wrote:
> ASoC machine driver can use snd_soc_{of_}get_dlc() (A) to get DAI name
> for dlc (snd_soc_dai_link_component). In this function call
> dlc->dai_name is parsed via snd_soc_dai_name_get() (B).
> 
> (A)	int snd_soc_get_dlc(...)
> 	{
> 		...
> (B)		dlc->dai_name = snd_soc_dai_name_get(dai);
> 		...
> 	}
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: soc-core.c: Prefer to return dai->driver->name in snd_soc_dai_name_get()
      commit: 755bb9a44f52dcc386c8db84d7c5a0f94ee95640

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