linux-kernel - Re: [PATCH][next] regulator: palmas: remove redundant initialization of pointer pdata

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: <169990443689.3294075.9581324276633996428.b4-ty@kernel.org>
Date:   Mon, 13 Nov 2023 19:40:36 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Tony Lindgren <tony@...mide.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        linux-omap@...r.kernel.org, Colin Ian King <colin.i.king@...il.com>
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH][next] regulator: palmas: remove redundant
 initialization of pointer pdata

On Sat, 11 Nov 2023 19:53:30 +0000, Colin Ian King wrote:
> Pointer pdata is being initialized with a value that is never read. It is
> being re-assigned later on with the return from a devm_kzalloc call.
> Remove the redundant initialization, cleans up clang scan build warning:
> 
> drivers/regulator/palmas-regulator.c:1597:36: warning: Value stored
> to 'pdata' during its initialization 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: palmas: remove redundant initialization of pointer pdata
      commit: 1fc2e768ff28f096e9fb6438f0d01c3851c7cd68

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