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
Subject: Re: [PATCH 0/6] thermal/cpu_cooling: Minor cleanups
Date: Wed, 12 Aug 2015 15:47:19 +0530 [thread overview]
Message-ID: <20150812101719.GB32432@linux> (raw)
In-Reply-To: <20150804085625.GB15655@linux>
On 04-08-15, 14:26, Viresh Kumar wrote:
> On 30-07-15, 12:40, Viresh Kumar wrote:
> > 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.
>
> Ping !
Another Ping :)
--
viresh
next prev parent reply other threads:[~2015-08-12 10:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 7:10 [PATCH 0/6] thermal/cpu_cooling: Minor cleanups Viresh Kumar
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 ` 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 ` 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 ` 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 ` 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 ` Viresh Kumar
2015-07-30 7:10 ` [PATCH 6/6] thermal/cpu_cooling: update policy limits if clipped_freq < policy->max Viresh Kumar
2015-07-30 7:10 ` Viresh Kumar
2015-08-04 8:56 ` [PATCH 0/6] thermal/cpu_cooling: Minor cleanups Viresh Kumar
2015-08-12 10:17 ` Viresh Kumar [this message]
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=20150812101719.GB32432@linux \
--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 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.