From: Viresh Kumar <viresh.kumar@linaro.org>
To: rjw@rjwysocki.net
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
arvind.chauhan@arm.com, srivatsa@mit.edu, skannan@codeaurora.org,
ybu@qti.qualcomm.com, Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V1 Resend 0/4] CPUFreq: Bug fixes & cleanups
Date: Thu, 17 Jul 2014 10:48:24 +0530 [thread overview]
Message-ID: <cover.1405573982.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
As discussed here:
https://www.mail-archive.com/stable@vger.kernel.org/msg87645.html
This is another attempt to fix an important bug and cleanups around it.
First patch is the real fix (Accumulated all Reviewed/Tested-by's) and *should*
go in 3.16-rc*.
Others are useful cleanups around it to beautify the code, and can go later in
3.17.
Based over: 3.16-rc4
Viresh Kumar (4):
cpufreq: move policy kobj to policy->cpu at resume
cpufreq: don't restore policy->cpus on failure to move kobj
cpufreq: propagate error returned by kobject_move()
cpufreq: move policy kobj from update_policy_cpu()
drivers/cpufreq/cpufreq.c | 68 +++++++++++++++++++++--------------------------
1 file changed, 31 insertions(+), 37 deletions(-)
--
2.0.0.rc2
next reply other threads:[~2014-07-17 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 5:18 Viresh Kumar [this message]
2014-07-17 5:18 ` [PATCH V1 Resend 1/4] cpufreq: move policy kobj to policy->cpu at resume Viresh Kumar
2014-07-18 0:57 ` Rafael J. Wysocki
2014-07-17 5:18 ` [PATCH V1 Resend 2/4] cpufreq: don't restore policy->cpus on failure to move kobj Viresh Kumar
2014-07-17 5:18 ` [PATCH V1 Resend 3/4] cpufreq: propagate error returned by kobject_move() Viresh Kumar
2014-07-17 5:18 ` [PATCH V1 Resend 4/4] cpufreq: move policy kobj from update_policy_cpu() 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=cover.1405573982.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=skannan@codeaurora.org \
--cc=srivatsa@mit.edu \
--cc=ybu@qti.qualcomm.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).