linux-kernel - Re: [PATCH] regmap: maple: Fix uninitialized symbol 'ret' warnings

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: <171173750738.1608278.15466912319940390970.b4-ty@kernel.org>
Date: Fri, 29 Mar 2024 18:38:27 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH] regmap: maple: Fix uninitialized symbol 'ret' warnings

On Fri, 29 Mar 2024 14:46:30 +0000, Richard Fitzgerald wrote:
> Fix warnings reported by smatch by initializing local 'ret' variable
> to 0.
> 
> drivers/base/regmap/regcache-maple.c:186 regcache_maple_drop()
> error: uninitialized symbol 'ret'.
> drivers/base/regmap/regcache-maple.c:290 regcache_maple_sync()
> error: uninitialized symbol 'ret'.
> 
> [...]

Applied to

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

Thanks!

[1/1] regmap: maple: Fix uninitialized symbol 'ret' warnings
      commit: eaa03486d932572dfd1c5f64f9dfebe572ad88c0

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