linux-kernel - Re: [PATCH] firmware: cs_dsp: Ensure cs_dsp_load[

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: <174291786934.56229.8841259212687977896.b4-ty@kernel.org>
Date: Tue, 25 Mar 2025 15:51:09 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: npache@...hat.com, linux-sound@...r.kernel.org, 
 linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] firmware: cs_dsp: Ensure cs_dsp_load[_coeff]() returns
 0 on success

On Sun, 23 Mar 2025 17:05:29 +0000, Richard Fitzgerald wrote:
> Set ret = 0 on successful completion of the processing loop in
> cs_dsp_load() and cs_dsp_load_coeff() to ensure that the function
> returns 0 on success.
> 
> All normal firmware files will have at least one data block, and
> processing this block will set ret == 0, from the result of either
> regmap_raw_write() or cs_dsp_parse_coeff().
> 
> [...]

Applied to

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

Thanks!

[1/1] firmware: cs_dsp: Ensure cs_dsp_load[_coeff]() returns 0 on success
      commit: 2593f7e0dc93a898a84220b3fb180d86f1ca8c60

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