linux-kernel - Re: [PATCH] ASoC: soc-pcm.c: Complete the active count for components without DAIs

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: <170292050439.89121.5834781324201085971.b4-ty@kernel.org>
Date: Mon, 18 Dec 2023 17:28:24 +0000
From: Mark Brown <broonie@...nel.org>
To: lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.com, 
 linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Chancel Liu <chancel.liu@....com>
Subject: Re: [PATCH] ASoC: soc-pcm.c: Complete the active count for
 components without DAIs

On Mon, 04 Dec 2023 19:15:32 +0800, Chancel Liu wrote:
> Some components like platforms don't have DAIs. If the active count of
> these components is ignored pinctrl may be wrongly selected between
> default and sleep state. So need to increment or decrement the active
> count for components without DAIs to avoid it.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: soc-pcm.c: Complete the active count for components without DAIs
      commit: 8f039360897bdd2f1f455b46a7f504b677405913

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