From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
preeti.lkml@gmail.com
Subject: Re: [PATCH V2 0/9] CPUFreq: governors: further cleanups
Date: Thu, 3 Sep 2015 10:14:54 +0530 [thread overview]
Message-ID: <20150903044454.GH13140@linux> (raw)
In-Reply-To: <cover.1437999691.git.viresh.kumar@linaro.org>
On 27-07-15, 17:58, Viresh Kumar wrote:
> Hi Rafael,
>
> This series fixes few more possible race conditions. Over that there is
> some non-trivial cleanup, in order to simplify code.
>
> Preeti did review some of them before she left and shared concerns on
> others, all that is sorted out now.
>
> V1->V2:
> - Dropped 2/10 from V1 as it wasn't required
> - 3/10 saw some changes due to above patch being dropped
> - 7/10 changed a bit as we check for pending work items by looking at
> shared->policy, rather than calling delayed_work_pending. We wanted to
> check if governor is operational or not and the new check is enough
> for that.
>
> Viresh Kumar (9):
> cpufreq: Use __func__ to print function's name
> cpufreq: conservative: remove 'enable' field
> cpufreq: ondemand: only queue canceled works from
> update_sampling_rate()
> cpufreq: governor: Drop __gov_queue_work()
> cpufreq: ondemand: Drop unnecessary locks from update_sampling_rate()
> cpufreq: ondemand: queue work for policy->cpus together
> cpufreq: ondemand: update sampling rate immidiately
> cpufreq: governor: Quit work-handlers early if governor is stopped
> cpufreq: Get rid of ->governor_enabled and its lock
I thought you had some review comment for this series?
--
viresh
next prev parent reply other threads:[~2015-09-03 4:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 12:28 [PATCH V2 0/9] CPUFreq: governors: further cleanups Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 1/9] cpufreq: Use __func__ to print function's name Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-07 23:42 ` Rafael J. Wysocki
2015-07-27 12:28 ` [PATCH V2 2/9] cpufreq: conservative: remove 'enable' field Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-08 0:17 ` Rafael J. Wysocki
2015-09-08 1:33 ` Viresh Kumar
2015-09-08 1:40 ` [PATCH V3 " Viresh Kumar
2015-09-08 1:40 ` Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 3/9] cpufreq: ondemand: only queue canceled works from update_sampling_rate() Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-08 1:11 ` Rafael J. Wysocki
2015-09-08 1:58 ` Viresh Kumar
2015-09-09 1:06 ` Rafael J. Wysocki
2015-09-09 2:30 ` Viresh Kumar
2015-09-09 20:10 ` Rafael J. Wysocki
2015-07-27 12:28 ` [PATCH V2 4/9] cpufreq: governor: Drop __gov_queue_work() Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-08 1:15 ` Rafael J. Wysocki
2015-09-08 2:00 ` Viresh Kumar
2015-09-09 1:04 ` Rafael J. Wysocki
2015-07-27 12:28 ` [PATCH V2 5/9] cpufreq: ondemand: Drop unnecessary locks from update_sampling_rate() Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 6/9] cpufreq: ondemand: queue work for policy->cpus together Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-08 1:33 ` Rafael J. Wysocki
2015-09-08 2:11 ` Viresh Kumar
2015-09-08 2:13 ` Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 7/9] cpufreq: ondemand: update sampling rate immidiately Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 8/9] cpufreq: governor: Quit work-handlers early if governor is stopped Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-07-27 12:28 ` [PATCH V2 9/9] cpufreq: Get rid of ->governor_enabled and its lock Viresh Kumar
2015-07-27 12:28 ` Viresh Kumar
2015-09-03 4:44 ` Viresh Kumar [this message]
2015-09-04 14:47 ` [PATCH V2 0/9] CPUFreq: governors: further cleanups Rafael J. Wysocki
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=20150903044454.GH13140@linux \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=preeti.lkml@gmail.com \
--cc=rjw@rjwysocki.net \
/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.