From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>, Stephen Boyd <sboyd@codeaurora.org>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V2 0/4] PM / OPP: Fixes
Date: Thu, 5 Nov 2015 14:21:17 +0530 [thread overview]
Message-ID: <cover.1446713282.git.viresh.kumar@linaro.org> (raw)
Hi Rafael,
V1 only contained a single patch, i.e. 2/4 from this series. And then
there were few suggestions to incorporate.
All are marked for stable 4.3, as this got changed recently.
I have tested it on exynos (Yeah, I was able to reproduce the lockdep
with few config changes).
Viresh Kumar (4):
PM / OPP: Propagate error properly from dev_pm_opp_set_sharing_cpus()
PM / OPP: Protect updates to list_dev with mutex
PM / OPP: Hold dev_opp_list_lock for writers
PM / OPP: Add opp_rcu_lockdep_assert() to _find_device_opp()
drivers/base/power/opp/core.c | 21 +++++++++++++++++----
drivers/base/power/opp/cpu.c | 10 +++++-----
drivers/base/power/opp/opp.h | 3 +++
3 files changed, 25 insertions(+), 9 deletions(-)
--
2.6.2.198.g614a2ac
next reply other threads:[~2015-11-05 8:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-05 8:51 Viresh Kumar [this message]
2015-11-05 8:51 ` [PATCH V2 1/4] PM / OPP: Propagate error properly from dev_pm_opp_set_sharing_cpus() Viresh Kumar
2015-11-05 8:51 ` [PATCH V2 2/4] PM / OPP: Protect updates to list_dev with mutex Viresh Kumar
2015-11-05 8:51 ` [PATCH V2 3/4] PM / OPP: Hold dev_opp_list_lock for writers Viresh Kumar
2015-11-05 8:51 ` [PATCH V2 4/4] PM / OPP: Add opp_rcu_lockdep_assert() to _find_device_opp() Viresh Kumar
2015-11-07 1:06 ` [PATCH V2 0/4] PM / OPP: Fixes 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=cover.1446713282.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).