From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regulator fixes for v5.11-rc5
Date: Tue, 26 Jan 2021 12:44:33 +0000 [thread overview]
Message-ID: <20210126124529.37C7123104@mail.kernel.org> (raw)
The following changes since commit 7c53f6b671f4aba70ff15e1b05148b10d58c2837:
Linux 5.11-rc3 (2021-01-10 14:34:50 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v5.11-rc5
for you to fetch changes up to 14a71d509ac809dcf56d7e3ca376b15d17bd0ddd:
regulator: Fix lockdep warning resolving supplies (2021-01-22 14:03:07 +0000)
----------------------------------------------------------------
regulator: Fixes for v5.11
The main thing here is a change to make sure that we don't try to double
resolve the supply of a regulator if we have two probes going on
simultaneously, plus an incremental fix on top of that to resolve a
lockdep issue it introduced.
There's also a patch from Dmitry Osipenko adding stubs for some
functions to avoid build issues in consumers in some configurations.
----------------------------------------------------------------
David Collins (1):
regulator: core: avoid regulator_resolve_supply() race condition
Dmitry Osipenko (1):
regulator: consumer: Add missing stubs to regulator/consumer.h
Mark Brown (2):
Merge v5.11-rc3
regulator: Fix lockdep warning resolving supplies
drivers/regulator/core.c | 44 ++++++++++++++++++++++++++++----------
include/linux/regulator/consumer.h | 30 ++++++++++++++++++++++++++
2 files changed, 63 insertions(+), 11 deletions(-)
next reply other threads:[~2021-01-26 13:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 12:44 Mark Brown [this message]
2021-01-26 19:07 ` [GIT PULL] regulator fixes for v5.11-rc5 pr-tracker-bot
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=20210126124529.37C7123104@mail.kernel.org \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).