From: Muhammad Falak R Wani <falakreyaz@gmail.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Muhammad Falak R Wani <falakreyaz@gmail.com>
Subject: [PATCH 1/1] fix cpufreq/cpufreq.c some coding style issues
Date: Sun, 23 Aug 2015 21:09:19 +0530 [thread overview]
Message-ID: <1440344359-7051-1-git-send-email-falakreyaz@gmail.com> (raw)
Hi,
This patch fixes issues in coding style, of a missing blank line after
declarations.
Best,
mfrw
Signed-off-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
---
drivers/cpufreq/cpufreq.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
index 8ae655c..5aea659 100644
--- a/drivers/cpufreq/cpufreq.c
+++ b/drivers/cpufreq/cpufreq.c
@@ -718,6 +718,7 @@ static ssize_t show_bios_limit(struct cpufreq_policy *policy, char *buf)
{
unsigned int limit;
int ret;
+
if (cpufreq_driver->bios_limit) {
ret = cpufreq_driver->bios_limit(policy->cpu, &limit);
if (!ret)
@@ -815,6 +816,7 @@ unlock:
static void cpufreq_sysfs_release(struct kobject *kobj)
{
struct cpufreq_policy *policy = to_policy(kobj);
+
pr_debug("last reference is dropped\n");
complete(&policy->kobj_unregister);
}
@@ -2129,6 +2131,7 @@ EXPORT_SYMBOL_GPL(cpufreq_unregister_governor);
int cpufreq_get_policy(struct cpufreq_policy *policy, unsigned int cpu)
{
struct cpufreq_policy *cpu_policy;
+
if (!policy)
return -EINVAL;
--
1.9.1
next reply other threads:[~2015-08-23 15:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 15:39 Muhammad Falak R Wani [this message]
[not found] ` <CAK-LDbKT0KX4T9Zj3+2hWfBW8KExKst-TL82i+Ta+pnhqBLqYw@mail.gmail.com>
2015-08-24 4:23 ` [PATCH 1/1] fix cpufreq/cpufreq.c some coding style issues Viresh Kumar
2015-08-24 4:35 ` Vaishali Thakkar
2015-08-24 4:24 ` Viresh Kumar
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=1440344359-7051-1-git-send-email-falakreyaz@gmail.com \
--to=falakreyaz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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