From: Fabio Baltieri <fabio.baltieri@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com
Subject: Re: [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors
Date: Thu, 31 Jan 2013 19:50:04 +0100 [thread overview]
Message-ID: <20130131185004.GB20164@balto.lan> (raw)
In-Reply-To: <118c59263751862b1750ed9f96639a4e70069e66.1359653181.git.viresh.kumar@linaro.org>
On Thu, Jan 31, 2013 at 10:58:02PM +0530, Viresh Kumar wrote:
> With the inclusion of following patches:
>
> 9f4eb10 cpufreq: conservative: call dbs_check_cpu only when necessary
> 772b4b1 cpufreq: ondemand: call dbs_check_cpu only when necessary
>
> code redundancy is introduced again. Get rid of it.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
Hi,
Tested-by: Fabio Baltieri <fabio.baltieri@linaro.org>
Thanks,
Fabio
--
Fabio Baltieri
next prev parent reply other threads:[~2013-01-31 18:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 17:28 [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field Viresh Kumar
[not found] ` <09a94ff044ff6a6f7a5d953c3b1f3102c1dc50cf.1359653181.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2013-01-31 17:28 ` [PATCH 2/2] cpufreq: governors: Remove code redundancy between governors Viresh Kumar
2013-01-31 18:50 ` Fabio Baltieri [this message]
2013-01-31 22:23 ` Rafael J. Wysocki
2013-01-31 22:51 ` Fabio Baltieri
2013-02-01 2:31 ` Viresh Kumar
2013-02-01 2:38 ` Viresh Kumar
2013-02-01 22:32 ` Rafael J. Wysocki
2013-01-31 17:29 ` [PATCH 1/2] cpufreq: governors: Get rid of dbs_data->enable field Viresh Kumar
2013-01-31 18:44 ` Fabio Baltieri
2013-02-01 3:52 ` Viresh Kumar
2013-02-01 6:44 ` 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=20130131185004.GB20164@balto.lan \
--to=fabio.baltieri@linaro.org \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--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