regulator: tps65219: regulator: tps65219: Fix error codes in probe()
PATCH 1/1 regulator: tps65219: regulator: tps65219: Fix error codes in probe()
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.
---
This is a rebase of a patch I sent earlier:
https://lore.kernel.org/all/[email protected]/
--- drivers/regulator/tps65219-regulator.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/regulator/tps65219-regulator.c +6 -6
@@ -454,9 +454,9 @@ static int tps65219_regulator_probe(struct platform_device *pdev) irq_type->irq_name, irq_data);if (error) -return dev_err_probe (tps->dev,PTR_ERR (rdev), -"Failed to request %s IRQ %d: %d\n" , - irq_type->irq_name, irq, error); +return dev_err_probe (tps->dev, error, +"Failed to request %s IRQ %d\n" , + irq_type->irq_name, irq); }for (i =0 ; i < pmic->dev_irq_size; ++i) {
@@ -477,9 +477,9 @@ static int tps65219_regulator_probe(struct platform_device *pdev) irq_type->irq_name, irq_data);if (error) -return dev_err_probe (tps->dev,PTR_ERR (rdev), -"Failed to request %s IRQ %d: %d\n" , - irq_type->irq_name, irq, error); +return dev_err_probe (tps->dev, error, +"Failed to request %s IRQ %d\n" , + irq_type->irq_name, irq); }return 0 ;
Signature · 1 line
2.47.2
Mark Brown
maintainerQuoted 8 lines · Dan Carpenter
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