linux-kernel - Re: [PATCH] ASoC: arizona/madera: use fsleep() in up/down DAPM event delays.

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: <173885349425.198179.4718145896745119973.b4-ty@kernel.org>
Date: Thu, 06 Feb 2025 14:51:34 +0000
From: Mark Brown <broonie@...nel.org>
To: Jaroslav Kysela <perex@...ex.cz>, 
 Vitaly Rodionov <vitalyr@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: arizona/madera: use fsleep() in up/down DAPM
 event delays.

On Wed, 05 Feb 2025 16:08:46 +0000, Vitaly Rodionov wrote:
> Using `fsleep` instead of `msleep` resolves some customer complaints
> regarding the precision of up/down DAPM event timing. `fsleep()`
> automatically selects the appropriate sleep function, making the delay
> time more predictable.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: arizona/madera: use fsleep() in up/down DAPM event delays.
      commit: 679074942c2502a95842a80471d8fb718165ac77

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