linux-kernel - Re: [PATCH] ASoC: pcm: perform power-down delay checks a bit faster

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: <772a45aeefeb0e63b85d9af17c971e2c@manjaro.org>
Date: Tue, 09 Apr 2024 22:51:05 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: Mark Brown <broonie@...nel.org>
Cc: linux-sound@...r.kernel.org, lgirdwood@...il.com, perex@...ex.cz,
 tiwai@...e.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ASoC: pcm: perform power-down delay checks a bit faster

On 2024-04-09 22:43, Mark Brown wrote:
> On Tue, 09 Apr 2024 19:56:36 +0200, Dragan Simic wrote:
>> When checking whether the power-down delay should be ignored for a 
>> specific
>> PCM runtime, there's no need to keep going through all DAI link 
>> components
>> after any of them is found to be configured to use the power-down 
>> delay.
>> 
>> While there, fix a small typo in one of the comment blocks.
>> 
>> 
>> [...]
> 
> Applied to
> 
>    https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git 
> for-next
> 
> Thanks!
> 
> [1/1] ASoC: pcm: perform power-down delay checks a bit faster
>       commit: f78bf2c933c9cb3b61215378664f83c5abd25374

Great, thanks!

> 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