Re: [PATCH] regulator: core: do not report EPROBE_DEFER as error.

On Wed, Apr 17, 2019 at 07:05:52PM +0200, Jorge Ramirez wrote: > On 4/17/19 17:46, Mark Brown wrote: > > Please leave at least a debug log in place, it's not good to just > > silently fail - even if we will retry someone might still need some help > > debugging (eg, figuring out that they need to

Re: [PATCH] regulator: core: do not report EPROBE_DEFER as error.

On 4/17/19 17:46, Mark Brown wrote: > On Wed, Apr 17, 2019 at 10:54:11AM +0200, Jorge Ramirez-Ortiz wrote: >> Do not log a temporary failure to get a regulator (EPROBE_DEFER) while >> the driver is requesting retries. > >> -dev_err(dev, "Failed to get supply '%s': %d\n", >> -

Re: [PATCH] regulator: core: do not report EPROBE_DEFER as error.

On Wed, Apr 17, 2019 at 10:54:11AM +0200, Jorge Ramirez-Ortiz wrote: > Do not log a temporary failure to get a regulator (EPROBE_DEFER) while > the driver is requesting retries. > - dev_err(dev, "Failed to get supply '%s': %d\n", > - consumers[i].sup

[PATCH] regulator: core: do not report EPROBE_DEFER as error.

Do not log a temporary failure to get a regulator (EPROBE_DEFER) while the driver is requesting retries. Signed-off-by: Jorge Ramirez-Ortiz --- drivers/regulator/core.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/regulator/core.c b/drivers/regulator/core.c in