linux-kernel - Re: [PATCH v2] regulator: tps65219: use IS

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <167405853919.940051.11907042713819434692.b4-ty@kernel.org>
Date:   Wed, 18 Jan 2023 16:15:39 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...radead.org>
Cc:     Jerome Neanne <jneanne@...libre.com>,
        Tony Lindgren <tony@...mide.com>, linux-omap@...r.kernel.org,
        Liam Girdwood <lgirdwood@...il.com>
Subject: Re: [PATCH v2] regulator: tps65219: use IS_ERR() to detect an
 error pointer

On Sat, 14 Jan 2023 10:57:36 -0800, Randy Dunlap wrote:
> Fix pointer comparison to integer warning from gcc & sparse:
> 
> GCC:
> ../drivers/regulator/tps65219-regulator.c:370:26: warning: ordered comparison of pointer with integer zero [-Wextra]
>   370 |                 if (rdev < 0) {
>       |                          ^
> 
> [...]

Applied to

   broonie/regulator.git for-next

Thanks!

[1/1] regulator: tps65219: use IS_ERR() to detect an error pointer
      commit: 2bbba115c3c9a647bcb3201b014fcc3728fe75c8

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