From: Viresh Kumar <viresh.kumar@linaro.org>
To: edubezval@gmail.com
Cc: linaro-kernel@lists.linaro.org, rui.zhang@intel.com,
linux-pm@vger.kernel.org, radivoje.jovanovic@linux.intel.com,
punit.agrawal@arm.com, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/6] thermal/cpu_cooling: Minor cleanups
Date: Thu, 30 Jul 2015 12:40:29 +0530 [thread overview]
Message-ID: <cover.1438239727.git.viresh.kumar@linaro.org> (raw)
Eduardo,
Radivoje and Punit asked me to look into a patch Radivoje has posted
recently and that got me to fix few things. It doesn't do anything
related to what Radivoje had in his patch though.
Viresh Kumar (6):
thermal/cpu_cooling: No need to initialize max_freq to 0
thermal/cpu_cooling: quit early after updating policy
thermal/cpu_cooling: convert 'switch' block to 'if' block in notifier
thermal/cpu_cooling: rename cpufreq_val as clipped_freq
thermal/cpu_cooling: rename max_freq as clipped_freq in notifier
thermal/cpu_cooling: update policy limits if clipped_freq <
policy->max
drivers/thermal/cpu_cooling.c | 46 ++++++++++++++++++++++++-------------------
1 file changed, 26 insertions(+), 20 deletions(-)
--
2.4.0
next reply other threads:[~2015-07-30 7:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 7:10 Viresh Kumar [this message]
2015-07-30 7:10 ` [PATCH 1/6] thermal/cpu_cooling: No need to initialize max_freq to 0 Viresh Kumar
2015-07-30 7:10 ` [PATCH 2/6] thermal/cpu_cooling: quit early after updating policy Viresh Kumar
2015-07-30 7:10 ` [PATCH 3/6] thermal/cpu_cooling: convert 'switch' block to 'if' block in notifier Viresh Kumar
2015-07-30 7:10 ` [PATCH 4/6] thermal/cpu_cooling: rename cpufreq_val as clipped_freq Viresh Kumar
2015-07-30 7:10 ` [PATCH 5/6] thermal/cpu_cooling: rename max_freq as clipped_freq in notifier Viresh Kumar
2015-07-30 7:10 ` [PATCH 6/6] thermal/cpu_cooling: update policy limits if clipped_freq < policy->max Viresh Kumar
2015-08-04 8:56 ` [PATCH 0/6] thermal/cpu_cooling: Minor cleanups Viresh Kumar
2015-08-12 10:17 ` Viresh Kumar
2015-08-14 4:59 ` Eduardo Valentin
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=cover.1438239727.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=edubezval@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=punit.agrawal@arm.com \
--cc=radivoje.jovanovic@linux.intel.com \
--cc=rui.zhang@intel.com \
/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 NNTP newsgroup(s).