From: Stratos Karafotis <stratosk@semaphore.gr>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>
Cc: "cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Henrik Nilsson <Karl.Henrik.Nilsson@gmail.com>
Subject: Re: [PATCH] cpufreq: ondemand: Remove redundant return statement
Date: Fri, 01 Nov 2013 20:13:26 +0200 [thread overview]
Message-ID: <5273EF46.7060703@semaphore.gr> (raw)
In-Reply-To: <7457887.jzoQrnelyS@vostro.rjw.lan>
On 11/01/2013 02:18 AM, Rafael J. Wysocki wrote:
> On Friday, November 01, 2013 12:09:16 AM Viresh Kumar wrote:
>> On 31 October 2013 23:57, Stratos Karafotis <stratosk@semaphore.gr> wrote:
>>> After commit dfa5bb622555d9da0df21b50f46ebdeef390041b
>>> "cpufreq: ondemand: Change the calculation of target frequency",
>>> this return statement is no longer needed.
>>>
>>> Reported-by: Henrik Nilsson <Karl.Henrik.Nilsson@gmail.com>
>>> Signed-off-by: Stratos Karafotis <stratosk@semaphore.gr>
>>> ---
>>> drivers/cpufreq/cpufreq_ondemand.c | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/drivers/cpufreq/cpufreq_ondemand.c b/drivers/cpufreq/cpufreq_ondemand.c
>>> index 32f26f6..18d4091 100644
>>> --- a/drivers/cpufreq/cpufreq_ondemand.c
>>> +++ b/drivers/cpufreq/cpufreq_ondemand.c
>>> @@ -168,7 +168,6 @@ static void od_check_cpu(int cpu, unsigned int load)
>>> dbs_info->rate_mult =
>>> od_tuners->sampling_down_factor;
>>> dbs_freq_increase(policy, policy->max);
>>> - return;
>>> } else {
>>> /* Calculate the next frequency proportional to load */
>>> unsigned int freq_next;
>>
>> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Queued up for 3.13, thanks!
>
Thank you both for your immediate response!
Stratos
prev parent reply other threads:[~2013-11-01 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 18:27 [PATCH] cpufreq: ondemand: Remove redundant return statement Stratos Karafotis
2013-10-31 18:39 ` Viresh Kumar
2013-11-01 0:18 ` Rafael J. Wysocki
2013-11-01 18:13 ` Stratos Karafotis [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=5273EF46.7060703@semaphore.gr \
--to=stratosk@semaphore.gr \
--cc=Karl.Henrik.Nilsson@gmail.com \
--cc=cpufreq@vger.kernel.org \
--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