linux-kernel - Re: [PATCH] ASoC: tegra: Use non-atomic timeout for ADX status register

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: <174220666440.86423.15072032170869045785.b4-ty@kernel.org>
Date: Mon, 17 Mar 2025 10:17:44 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-sound@...r.kernel.org, "Sheetal ." <sheetal@...dia.com>
Cc: linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org, 
 jonathanh@...dia.com, thierry.reding@...il.com, mkumard@...dia.com, 
 spujar@...dia.com, Ritu Chaudhary <rituc@...dia.com>
Subject: Re: [PATCH] ASoC: tegra: Use non-atomic timeout for ADX status
 register

On Tue, 11 Mar 2025 06:20:10 +0000, Sheetal . wrote:
> ADX startup() callback uses atomic poll timeout on ADX status register.
> 
> This is unnecessary because:
> 
> - The startup() callback itself is non-atomic.
> - The subsequent timeout call in the same function already uses a
>   non-atomic version.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tegra: Use non-atomic timeout for ADX status register
      commit: f1d742c35b659fb0122da0a8ff09ad9309cb29d8

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