From: Jean Delvare <khali@linux-fr.org>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: cpufreq@lists.linux.org.uk, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 2.6] cpufreq: two minor cleanups
Date: Tue, 28 Jun 2005 23:28:30 +0200 [thread overview]
Message-ID: <20050628232830.6630c526.khali@linux-fr.org> (raw)
Hi Dave,
Here are two possible cleanups in cpufreq.c:
* ret has no need to be unsigned in cpufreq_driver_target()
* ret has no need to be initialized in __cpufreq_governor()
Thanks.
Signed-off-by: Jean Delvare <khali@linux-fr.org>
drivers/cpufreq/cpufreq.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.12.orig/drivers/cpufreq/cpufreq.c 2005-06-21 21:25:31.000000000 +0200
+++ linux-2.6.12/drivers/cpufreq/cpufreq.c 2005-06-21 21:29:01.000000000 +0200
@@ -1130,7 +1130,7 @@
unsigned int target_freq,
unsigned int relation)
{
- unsigned int ret;
+ int ret;
policy = cpufreq_cpu_get(policy->cpu);
if (!policy)
@@ -1151,7 +1151,7 @@
static int __cpufreq_governor(struct cpufreq_policy *policy, unsigned int event)
{
- int ret = -EINVAL;
+ int ret;
if (!try_module_get(policy->governor->owner))
return -EINVAL;
--
Jean Delvare
reply other threads:[~2005-06-28 21:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050628232830.6630c526.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®