linux-kernel - Re: [PATCH] regulator: max14577: Add error check for max14577_read

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: <174827717705.619417.16011537123487299524.b4-ty@kernel.org>
Date: Mon, 26 May 2025 17:32:57 +0100
From: Mark Brown <broonie@...nel.org>
To: cw00.choi@...sung.com, krzk@...nel.org, lgirdwood@...il.com, 
 Wentao Liang <vulab@...as.ac.cn>
Cc: linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] regulator: max14577: Add error check for
 max14577_read_reg()

On Mon, 26 May 2025 10:56:27 +0800, Wentao Liang wrote:
> The function max14577_reg_get_current_limit() calls the function
> max14577_read_reg(), but does not check its return value. A proper
> implementation can be found in max14577_get_online().
> 
> Add a error check for the max14577_read_reg() and return error code
> if the function fails.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: max14577: Add error check for max14577_read_reg()
      commit: 65271f868cb1dca709ff69e45939bbef8d6d0b70

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