From: Viresh Kumar <viresh.kumar@linaro.org>
To: Muhammad Falak R Wani <falakreyaz@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH] cpufreq: cpufreq: Fix coding style issues
Date: Mon, 24 Aug 2015 09:55:51 +0530 [thread overview]
Message-ID: <20150824042551.GC5375@linux> (raw)
In-Reply-To: <1440348235-7789-1-git-send-email-falakreyaz@gmail.com>
On 23-08-15, 22:13, Muhammad Falak R Wani wrote:
> This patch introduces a blank line after declarations, which
> fix the checkpatch.pl warnings at 3 places.
>
> 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;
We don't really need a patch for this, unless Rafael wants to apply
this one :)
--
viresh
prev parent reply other threads:[~2015-08-24 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 16:43 [RESEND PATCH] cpufreq: cpufreq: Fix coding style issues Muhammad Falak R Wani
2015-08-24 4:25 ` Viresh Kumar [this message]
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=20150824042551.GC5375@linux \
--to=viresh.kumar@linaro.org \
--cc=falakreyaz@gmail.com \
--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 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.