linux-kernel - Re: [PATCH 0/2] ASoC: stm32: dfsdm: change rate limits

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <160219448332.29664.10143559083895905802.b4-ty@kernel.org>
Date:   Thu, 08 Oct 2020 23:01:51 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Olivier Moysan <olivier.moysan@...com>, lgirdwood@...il.com,
        arnaud.pouliquen@...com, tiwai@...e.com, perex@...ex.cz,
        alexandre.torgue@...com
Cc:     linux-kernel@...r.kernel.org, alsa-devel@...a-project.org,
        linux-arm-kernel@...ts.infradead.org,
        linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH 0/2] ASoC: stm32: dfsdm: change rate limits

On Wed, 7 Oct 2020 17:34:57 +0200, Olivier Moysan wrote:
> Widening of the supported rate range in the STM32 DFSDM driver.
> The rates were previously limited to 8kHz, 16kHz and 32kHz.
> Allow rate capture in the whole range 8kHz-48kHz as there is no hardware
> limitation to support it.
> Actual sample resolution is dependent on audio rate and DFSDM configuration.
> Add a trace to allow simple check of sample resolution.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: stm32: dfsdm: change rate limits
      commit: 6101bf71192f543799a796274e160f7dfc10f2d2
[2/2] ASoC: stm32: dfsdm: add actual resolution trace
      commit: 41bceb1272164ee2a6fd1ac3bed97043c94b6636

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