[PATCH] regulator: Lower priority of logging when setting supply

[PATCH] regulator: Lower priority of logging when setting supply

[Mark Brown]

We lowered all the other constraint related log messages to debug level so
lower the logging of what supplies we're configuring to debug level too.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
 drivers/regulator/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c
index 4b22c3276d58..26bee444fc70 100644
--- a/drivers/regulator/core.c
+++ b/drivers/regulator/core.c
@@ -1571,7 +1571,7 @@ static int set_supply(struct regulator_dev *rdev,
 {
 	int err;
 
-	rdev_info(rdev, "supplied by %s\n", rdev_get_name(supply_rdev));
+	rdev_dbg(rdev, "supplied by %s\n", rdev_get_name(supply_rdev));
 
 	if (!try_module_get(supply_rdev->owner))
 		return -ENODEV;
-- 
2.20.1

Re: [PATCH] regulator: Lower priority of logging when setting supply

[Mark Brown]

On Wed, 29 Sep 2021 15:07:17 +0100, Mark Brown wrote:
> We lowered all the other constraint related log messages to debug level so
> lower the logging of what supplies we're configuring to debug level too.
> 
> 

Applied to

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

Thanks!

[1/1] regulator: Lower priority of logging when setting supply
      commit: 35d114699b90c8b2c568c48f78adeb913d81bcc1

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