linux-kernel - Re: [PATCH][next] regulator: core: Remove redundant assignment to variable possible

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: <170847670760.72396.11946631659826067398.b4-ty@kernel.org>
Date: Wed, 21 Feb 2024 00:51:47 +0000
From: Mark Brown <broonie@...nel.org>
To: Liam Girdwood <lgirdwood@...il.com>, 
 Colin Ian King <colin.i.king@...il.com>
Cc: kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] regulator: core: Remove redundant assignment to
 variable possible_uV

On Fri, 16 Feb 2024 13:49:18 +0000, Colin Ian King wrote:
> The variable possible_uV being assigned a value that is never read, the
> control flow via the following goto statement takes a path where the
> variable is not accessed. The assignment is redundant and can be removed.
> 
> Cleans up clang scan build warning:
> drivers/regulator/core.c:3935:3: warning: Value stored to 'possible_uV'
> is never read [deadcode.DeadStores]
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: core: Remove redundant assignment to variable possible_uV
      commit: 055100d1a3b27ce154b3e3041d3cef24778821b3

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