All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH] cpufreq: cpu0: Do not print error message when deferring
@ 2014-08-04 12:48 ` Markus Pargmann
  0 siblings, 0 replies; 4+ messages in thread
From: Markus Pargmann @ 2014-08-04 12:48 UTC (permalink / raw)
  To: Rafael J. Wysocki, Viresh Kumar
  Cc: linux-pm, linux-arm-kernel, kernel, Markus Pargmann

-EPROBE_DEFER is no real error. We are just waiting unti the necessary
components are ready. The driver core infrastructure will also print an
appropriate info message.

This patch changes the error message to a debug message.

Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
---
 drivers/cpufreq/cpufreq-cpu0.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
index ee1ae303a07c..26405d5c7a1f 100644
--- a/drivers/cpufreq/cpufreq-cpu0.c
+++ b/drivers/cpufreq/cpufreq-cpu0.c
@@ -137,7 +137,7 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev)
 		 * not yet registered, we should try defering probe.
 		 */
 		if (PTR_ERR(cpu_reg) == -EPROBE_DEFER) {
-			dev_err(cpu_dev, "cpu0 regulator not ready, retry\n");
+			dev_dbg(cpu_dev, "cpu0 regulator not ready, retry\n");
 			ret = -EPROBE_DEFER;
 			goto out_put_node;
 		}
-- 
2.0.1


^ permalink raw reply related	[flat|nested] 4+ messages in thread

* [PATCH] cpufreq: cpu0: Do not print error message when deferring
@ 2014-08-04 12:48 ` Markus Pargmann
  0 siblings, 0 replies; 4+ messages in thread
From: Markus Pargmann @ 2014-08-04 12:48 UTC (permalink / raw)
  To: linux-arm-kernel

-EPROBE_DEFER is no real error. We are just waiting unti the necessary
components are ready. The driver core infrastructure will also print an
appropriate info message.

This patch changes the error message to a debug message.

Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
---
 drivers/cpufreq/cpufreq-cpu0.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
index ee1ae303a07c..26405d5c7a1f 100644
--- a/drivers/cpufreq/cpufreq-cpu0.c
+++ b/drivers/cpufreq/cpufreq-cpu0.c
@@ -137,7 +137,7 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev)
 		 * not yet registered, we should try defering probe.
 		 */
 		if (PTR_ERR(cpu_reg) == -EPROBE_DEFER) {
-			dev_err(cpu_dev, "cpu0 regulator not ready, retry\n");
+			dev_dbg(cpu_dev, "cpu0 regulator not ready, retry\n");
 			ret = -EPROBE_DEFER;
 			goto out_put_node;
 		}
-- 
2.0.1

^ permalink raw reply related	[flat|nested] 4+ messages in thread

* Re: [PATCH] cpufreq: cpu0: Do not print error message when deferring
  2014-08-04 12:48 ` Markus Pargmann
@ 2014-08-04 13:34   ` Viresh Kumar
  -1 siblings, 0 replies; 4+ messages in thread
From: Viresh Kumar @ 2014-08-04 13:34 UTC (permalink / raw)
  To: Markus Pargmann
  Cc: Rafael J. Wysocki, linux-pm, linux-arm-kernel, Sascha Hauer

On 4 August 2014 18:18, Markus Pargmann <mpa@pengutronix.de> wrote:
> -EPROBE_DEFER is no real error. We are just waiting unti the necessary
> components are ready. The driver core infrastructure will also print an
> appropriate info message.
>
> This patch changes the error message to a debug message.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
>  drivers/cpufreq/cpufreq-cpu0.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
> index ee1ae303a07c..26405d5c7a1f 100644
> --- a/drivers/cpufreq/cpufreq-cpu0.c
> +++ b/drivers/cpufreq/cpufreq-cpu0.c
> @@ -137,7 +137,7 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev)
>                  * not yet registered, we should try defering probe.
>                  */
>                 if (PTR_ERR(cpu_reg) == -EPROBE_DEFER) {
> -                       dev_err(cpu_dev, "cpu0 regulator not ready, retry\n");
> +                       dev_dbg(cpu_dev, "cpu0 regulator not ready, retry\n");
>                         ret = -EPROBE_DEFER;
>                         goto out_put_node;
>                 }

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [PATCH] cpufreq: cpu0: Do not print error message when deferring
@ 2014-08-04 13:34   ` Viresh Kumar
  0 siblings, 0 replies; 4+ messages in thread
From: Viresh Kumar @ 2014-08-04 13:34 UTC (permalink / raw)
  To: linux-arm-kernel

On 4 August 2014 18:18, Markus Pargmann <mpa@pengutronix.de> wrote:
> -EPROBE_DEFER is no real error. We are just waiting unti the necessary
> components are ready. The driver core infrastructure will also print an
> appropriate info message.
>
> This patch changes the error message to a debug message.
>
> Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> ---
>  drivers/cpufreq/cpufreq-cpu0.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/cpufreq-cpu0.c b/drivers/cpufreq/cpufreq-cpu0.c
> index ee1ae303a07c..26405d5c7a1f 100644
> --- a/drivers/cpufreq/cpufreq-cpu0.c
> +++ b/drivers/cpufreq/cpufreq-cpu0.c
> @@ -137,7 +137,7 @@ static int cpu0_cpufreq_probe(struct platform_device *pdev)
>                  * not yet registered, we should try defering probe.
>                  */
>                 if (PTR_ERR(cpu_reg) == -EPROBE_DEFER) {
> -                       dev_err(cpu_dev, "cpu0 regulator not ready, retry\n");
> +                       dev_dbg(cpu_dev, "cpu0 regulator not ready, retry\n");
>                         ret = -EPROBE_DEFER;
>                         goto out_put_node;
>                 }

Acked-by: Viresh Kumar <viresh.kumar@linaro.org>

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-08-04 13:34 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-04 12:48 [PATCH] cpufreq: cpu0: Do not print error message when deferring Markus Pargmann
2014-08-04 12:48 ` Markus Pargmann
2014-08-04 13:34 ` Viresh Kumar
2014-08-04 13:34   ` Viresh Kumar

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.