From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stratos Karafotis <stratosk@semaphore.gr>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cpufreq: Remove unnecessary braces
Date: Thu, 20 Mar 2014 05:36:36 +0530 [thread overview]
Message-ID: <CAKohpomLRH7QT71+N7_7AveKPU3rgQv37Ye6d=pUcKjC6shtEg@mail.gmail.com> (raw)
In-Reply-To: <532A2759.1000708@semaphore.gr>
On 20 March 2014 04:55, Stratos Karafotis <stratosk@semaphore.gr> wrote:
> I'm sorry for the inconvenience. I read again the CodingStyle (more carefully :) ).
> I'm sending the corrected patch with the single case of unnecessary braces.
>
> Thanks,
> Stratos
>
> ------------------------8<-----------------------
> Remove unnecessary braces from a single statement.
>
> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
> ---
> drivers/cpufreq/cpufreq.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/cpufreq/cpufreq.c b/drivers/cpufreq/cpufreq.c
> index e3aa9de..220c4a9 100644
> --- a/drivers/cpufreq/cpufreq.c
> +++ b/drivers/cpufreq/cpufreq.c
> @@ -1330,10 +1330,9 @@ static int __cpufreq_remove_dev_prepare(struct device *dev,
> if (new_cpu >= 0) {
> update_policy_cpu(policy, new_cpu);
>
> - if (!cpufreq_suspended) {
> + if (!cpufreq_suspended)
> pr_debug("%s: policy Kobject moved to cpu: %d from: %d\n",
> __func__, new_cpu, cpu);
> - }
> }
> }
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
prev parent reply other threads:[~2014-03-20 0:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 21:33 [PATCH] cpufreq: Remove unnecessary braces Stratos Karafotis
2014-03-19 22:45 ` Rafael J. Wysocki
2014-03-19 23:25 ` Stratos Karafotis
2014-03-20 0:06 ` 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='CAKohpomLRH7QT71+N7_7AveKPU3rgQv37Ye6d=pUcKjC6shtEg@mail.gmail.com' \
--to=viresh.kumar@linaro.org \
--cc=cpufreq@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=stratosk@semaphore.gr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).