linux-kernel - Re: [PATCH 0/2] ASoC: stm32: sai: fix kernel rate configuration

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: <174608148419.4032397.674149169345577452.b4-ty@kernel.org>
Date: Thu, 01 May 2025 15:38:04 +0900
From: Mark Brown <broonie@...nel.org>
To: Arnaud Pouliquen <arnaud.pouliquen@...s.st.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, Maxime Coquelin <mcoquelin.stm32@...il.com>, 
 Alexandre Torgue <alexandre.torgue@...s.st.com>, 
 Olivier Moysan <olivier.moysan@...s.st.com>
Cc: linux-sound@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] ASoC: stm32: sai: fix kernel rate configuration

On Wed, 30 Apr 2025 18:52:07 +0200, Olivier Moysan wrote:
> This patchset adds some checks on kernel minimum rate requirements.
> This avoids potential clock rate misconfiguration, when setting the
> kernel frequency on STM32MP2 SoCs.
> 
> Olivier Moysan (2):
>   ASoC: stm32: sai: skip useless iterations on kernel rate loop
>   ASoC: stm32: sai: add a check on minimal kernel frequency
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: stm32: sai: skip useless iterations on kernel rate loop
      commit: edea92770a3b6454dc796fc5436a3315bb402181
[2/2] ASoC: stm32: sai: add a check on minimal kernel frequency
      commit: cce34d113e2a592806abcdc02c7f8513775d8b20

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