linux-kernel - Re: [PATCH] ASoC: cs35l56: Alter error codes for calibration routine

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: <176279298704.56837.6472394807142684200.b4-ty@kernel.org>
Date: Mon, 10 Nov 2025 16:43:07 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org, 
 patches@...nsource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Alter error codes for calibration
 routine

On Mon, 10 Nov 2025 11:43:27 +0000, Richard Fitzgerald wrote:
> Adjust the error codes returned by the calibration debugfs files
> to provide a wider range of errors and make them more consistent.
> 
> There is a limited number of standard errors and it's not always
> easy to find an error code that accurately describes what happened.
> Additionally, user code often uses strerror() or something similar
> to report a generic error description. The original calibration
> code used a limited set of errors to attempt to avoid user error
> strings that would be confusing or unclear on a file read/write.
> However, this restricts the ability to provide informative errors.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Alter error codes for calibration routine
      commit: 772ada50282b0c80343c8989147db816961f571d

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