linux-kernel - Re: [PATCH next] ASoC: rt1320: Fix retry checking in rt1320_rae

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: <176642584614.925274.13974919096126577279.b4-ty@kernel.org>
Date: Mon, 22 Dec 2025 17:50:46 +0000
From: Mark Brown <broonie@...nel.org>
To: Shuming Fan <shumingf@...ltek.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Oder Chiou <oder_chiou@...ltek.com>, 
 Liam Girdwood <lgirdwood@...il.com>, Jaroslav Kysela <perex@...ex.cz>, 
 Takashi Iwai <tiwai@...e.com>, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] ASoC: rt1320: Fix retry checking in
 rt1320_rae_load()

On Sat, 20 Dec 2025 11:45:40 +0300, Dan Carpenter wrote:
> This loop iterates 200 times and then gives up.  The problem is that
> currently the loop exits with "retry" set to -1 on the failure path but
> the check for failure expects it to be 0.  Change from a post-op to a
> pre-op so that it exits with "retry" set to 0.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: rt1320: Fix retry checking in rt1320_rae_load()
      commit: c6bca73d699cfe00d3419566fdb2a45e112f44b0

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