All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
	Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
	linux-pm@vger.kernel.org,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Mason <slash.tmp@free.fr>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM / OPP: OF: Use pr_debug() instead of pr_err() while adding OPP table
Date: Wed, 12 Jul 2017 23:10:14 -0700	[thread overview]
Message-ID: <20170713061014.GU22780@codeaurora.org> (raw)
In-Reply-To: <3b5b0e789b7296f7b38f4ab9503a53031280a672.1499831484.git.viresh.kumar@linaro.org>

On 07/12, Viresh Kumar wrote:
> Some platforms add the OPPs dynamically from platform specific drivers
> instead of getting them statically from DT. The cpufreq-dt driver
> already ignores the return value of dev_pm_opp_of_cpumask_add_table() to
> not error out for such cases, but we still end up printing error message
> from that routine. That's not nice.
> 
> Convert the print message to use pr_debug() instead.
> 
> Reported-by: Mason <slash.tmp@free.fr>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---

Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project

  reply	other threads:[~2017-07-13  6:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12  3:51 [PATCH] PM / OPP: OF: Use pr_debug() instead of pr_err() while adding OPP table Viresh Kumar
2017-07-13  6:10 ` Stephen Boyd [this message]
2017-07-21 22:40   ` Rafael J. Wysocki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170713061014.GU22780@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=rjw@rjwysocki.net \
    --cc=slash.tmp@free.fr \
    --cc=vincent.guittot@linaro.org \
    --cc=viresh.kumar@linaro.org \
    --cc=vireshk@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.