From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 2/6] cpufreq: governor: Remove unnecessary bits from print message
Date: Wed, 18 May 2016 17:55:27 +0530 [thread overview]
Message-ID: <a676e03e63c25c0fed482706d98317b66a277252.1463574213.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1463574213.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1463574213.git.viresh.kumar@linaro.org>
pr_*() helpers already prefix the print messages with
"cpufreq_governor:" and similar details aren't required in the actual
message.
For example, the print message getting fixed looks like this before this
patch:
cpufreq_governor: cpufreq: Governor initialization failed (dbs_data kobject init error 0)
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
drivers/cpufreq/cpufreq_governor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq_governor.c b/drivers/cpufreq/cpufreq_governor.c
index be498d56dd69..45ca5aff88b2 100644
--- a/drivers/cpufreq/cpufreq_governor.c
+++ b/drivers/cpufreq/cpufreq_governor.c
@@ -458,7 +458,7 @@ static int cpufreq_governor_init(struct cpufreq_policy *policy)
goto out;
/* Failure, so roll back. */
- pr_err("cpufreq: Governor initialization failed (dbs_data kobject init error %d)\n", ret);
+ pr_err("initialization failed (dbs_data kobject init error %d)\n", ret);
policy->governor_data = NULL;
--
2.7.1.410.g6faf27b
next prev parent reply other threads:[~2016-05-18 12:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 12:25 [PATCH 0/6] cpufreq: minor cleanups Viresh Kumar
2016-05-18 12:25 ` [PATCH 1/6] cpufreq: governor: Remove prints from allocation failures Viresh Kumar
2016-05-18 12:25 ` Viresh Kumar [this message]
2016-05-18 12:25 ` [PATCH 3/6] cpufreq: schedutil: Improve prints messages with pr_fmt Viresh Kumar
2016-05-18 12:25 ` [PATCH 4/6] cpufreq: conservative: Remove declaration of cs_dbs_gov Viresh Kumar
2016-05-18 21:03 ` Rafael J. Wysocki
2016-05-19 2:13 ` Viresh Kumar
2016-05-18 12:25 ` [PATCH 5/6] cpufreq: Reuse gov_attr_* macros in schedutil governor Viresh Kumar
2016-05-18 21:01 ` Rafael J. Wysocki
2016-05-19 2:13 ` Viresh Kumar
2016-05-19 11:43 ` Rafael J. Wysocki
2016-05-18 12:25 ` [PATCH 6/6] cpufreq: governor: Create cpufreq_policy_apply_limits() Viresh Kumar
2016-05-18 21:06 ` [PATCH 0/6] cpufreq: minor cleanups 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=a676e03e63c25c0fed482706d98317b66a277252.1463574213.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).