From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Kevin Hilman <khilman@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Krzysztof Kozlowski <krzk@kernel.org>
Subject: [PATCH v3 0/8] PM / Domains: Bunch of small improvements and fixes
Date: Wed, 28 Jun 2017 16:56:15 +0200 [thread overview]
Message-ID: <20170628145623.20716-1-krzk@kernel.org> (raw)
Hi,
Changes since v2:
=================
1. Add Ulf's acks.
2. Re-order patches so the un-acked commits are at the end.
Changes since v1:
=================
1. Patch 2/8: Follow Ulf's advice and use genpd_lookup_dev() which also
solves risk of calling this for non-genpd (thus I added Ulf's
Reported-by).
The last patch is RFC as this brings small overhead.
Best regards,
Krzysztof
Krzysztof Kozlowski (8):
PM / Domains: Constify genpd pointer
PM / Domains: Handle safely genpd_syscore_switch() call on non-genpd
device
PM / Domains: Fix unsafe iteration over modified list of device links
PM / Domains: Fix unsafe iteration over modified list of domain
providers
PM / Domains: Fix unsafe iteration over modified list of domains
PM / Domains: Fix missing default_power_down_ok comment
PM / Domains: Add lockdep asserts for domains list mutex
PM / Domains: Add asserts for PM domain locks
drivers/base/power/domain.c | 63 +++++++++++++++++++++++++++---------
drivers/base/power/domain_governor.c | 12 +++----
2 files changed, 54 insertions(+), 21 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-28 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 14:56 Krzysztof Kozlowski [this message]
2017-06-28 14:56 ` [PATCH v3 1/8] PM / Domains: Constify genpd pointer Krzysztof Kozlowski
2017-06-28 14:56 ` [PATCH v3 2/8] PM / Domains: Handle safely genpd_syscore_switch() call on non-genpd device Krzysztof Kozlowski
2017-07-04 13:01 ` Geert Uytterhoeven
2017-07-04 18:10 ` Krzysztof Kozlowski
2017-07-04 18:19 ` Geert Uytterhoeven
2017-07-04 18:36 ` Krzysztof Kozlowski
2017-07-04 19:54 ` Rafael J. Wysocki
2017-07-04 20:05 ` Krzysztof Kozlowski
2017-07-04 20:12 ` Rafael J. Wysocki
2017-07-04 20:20 ` Krzysztof Kozlowski
2017-07-04 20:28 ` Rafael J. Wysocki
2017-06-28 14:56 ` [PATCH v3 3/8] PM / Domains: Fix unsafe iteration over modified list of device links Krzysztof Kozlowski
2017-06-28 14:56 ` [PATCH v3 4/8] PM / Domains: Fix unsafe iteration over modified list of domain providers Krzysztof Kozlowski
2017-06-28 14:56 ` [PATCH v3 5/8] PM / Domains: Fix unsafe iteration over modified list of domains Krzysztof Kozlowski
2017-06-28 14:56 ` [PATCH v3 6/8] PM / Domains: Fix missing default_power_down_ok comment Krzysztof Kozlowski
2017-06-28 14:56 ` [PATCH v3 7/8] PM / Domains: Add lockdep asserts for domains list mutex Krzysztof Kozlowski
2017-06-28 14:56 ` [RFC v3 8/8] PM / Domains: Add asserts for PM domain locks Krzysztof Kozlowski
2017-06-28 23:45 ` [PATCH v3 0/8] PM / Domains: Bunch of small improvements and 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=20170628145623.20716-1-krzk@kernel.org \
--to=krzk@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®