linux-kernel - Re: [PATCH] regulator: tps65219: regulator: tps65219: Fix error codes in probe()

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: <175562953472.246782.13325233916103955955.b4-ty@kernel.org>
Date: Tue, 19 Aug 2025 19:52:14 +0100
From: Mark Brown <broonie@...nel.org>
To: Shree Ramamoorthy <s-ramamoorthy@...com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Aaro Koskinen <aaro.koskinen@....fi>, 
 Andreas Kemnade <andreas@...nade.info>, Kevin Hilman <khilman@...libre.com>, 
 Roger Quadros <rogerq@...nel.org>, Tony Lindgren <tony@...mide.com>, 
 Liam Girdwood <lgirdwood@...il.com>, linux-omap@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH] regulator: tps65219: regulator: tps65219: Fix error
 codes in probe()

On Tue, 19 Aug 2025 12:40:41 +0300, Dan Carpenter wrote:
> There is a copy and paste error and we accidentally use "PTR_ERR(rdev)"
> instead of "error".  The "rdev" pointer is valid at this point.
> 
> Also there is no need to print the error code in the error message
> because dev_err_probe() already prints that.  So clean up the error
> message a bit.
> 
> [...]

Applied to

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

Thanks!

[1/1] regulator: tps65219: regulator: tps65219: Fix error codes in probe()
      commit: 11cd7a5c21db020b8001aedcae27bd3fa9e1e901

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