regulator: userspace-consumer: quiet device deferral
PATCH 1/1 regulator: userspace-consumer: quiet device deferral
Trying to use userspace-consumer when the required supplies have not yet been probed will throw an error message on deferral:
reg-userspace-consumer output-led-power: Failed to get supplies: -517
So, lets simply use dev_err_probe() instead of dev_err() to not print errors in case when driver probe is being deferred.
--- drivers/regulator/userspace-consumer.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
drivers/regulator/userspace-consumer.c +2 -4
@@ -158,10 +158,8 @@ static int regulator_userspace_consumer_probe(struct platform_device *pdev) ret =devm_regulator_bulk_get_exclusive (&pdev->dev, drvdata->num_supplies, drvdata->supplies); -if (ret) { -dev_err (&pdev->dev,"Failed to get supplies: %d\n" , ret); -return ret; - } +if (ret) +return dev_err_probe (&pdev->dev, ret,"Failed to get supplies\n" );platform_set_drvdata (pdev, drvdata);
Signature · 1 line
2.45.2
Mark Brown
maintainerQuoted 8 lines · Robert Marko
Trying to use userspace-consumer when the required supplies have not yet been probed will throw an error message on deferral:
reg-userspace-consumer output-led-power: Failed to get supplies: -517So, lets simply use
dev_err_probe()instead ofdev_err()to not print errors in case when driver probe is being deferred.[...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regulator: userspace-consumer: quiet device deferral
commit: 61a98ffc2081ac1e9070150932d9eb91d3935cf8
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