From: Dmitry Osipenko <digetx@gmail.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh+dt@kernel.org>
Cc: linux-tegra@vger.kernel.org, linux-omap@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/3] Coupled-regulators follow up
Date: Mon, 19 Nov 2018 00:56:15 +0300 [thread overview]
Message-ID: <20181118215619.21518-1-digetx@gmail.com> (raw)
Hi,
This is a follow up to [0].
What's changed in v2:
- The "Use ww_mutex for regulators locking" patch compiles now for the
drivers that are touching "rdev's" mutex, in a result regulator_[un]lock()
functions are public now.
- Added new patch to the series ("Keep regulators-list locked while
traversing the list") which further firms regulators locking.
- Changed commit description of the "Change regulator-coupled-max-spread
property" patch, saying that it's fine to change the binding because
property doesn't have any users yet. That was requested by Rob Herring
in the review comment to v1.
[0] https://patchwork.ozlabs.org/project/linux-tegra/list/?series=69250
Dmitry Osipenko (3):
regulator: core: Use ww_mutex for regulators locking
regulator: core: Properly handle case where supply is the couple
regulator: core: Keep regulators-list locked while traversing the list
drivers/regulator/core.c | 425 ++++++++++++++++++++------
drivers/regulator/da9210-regulator.c | 4 +-
drivers/regulator/stpmic1_regulator.c | 4 +-
drivers/regulator/wm8350-regulator.c | 4 +-
include/linux/regulator/driver.h | 6 +-
5 files changed, 339 insertions(+), 104 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-18 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-18 21:56 Dmitry Osipenko [this message]
2018-11-18 21:56 ` [PATCH v2] dt-bindings: regulator: Change regulator-coupled-max-spread property Dmitry Osipenko
2018-11-18 21:56 ` [PATCH v2 1/3] regulator: core: Use ww_mutex for regulators locking Dmitry Osipenko
2018-11-18 21:56 ` [PATCH v2 2/3] regulator: core: Properly handle case where supply is the couple Dmitry Osipenko
2018-11-18 21:56 ` [PATCH v2 3/3] regulator: core: Keep regulators-list locked while traversing the list Dmitry Osipenko
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=20181118215619.21518-1-digetx@gmail.com \
--to=digetx@gmail.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.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