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.10-rc2
Date: Thu, 05 Nov 2020 16:45:25 +0000 [thread overview]
Message-ID: <20201105164547.AE3AD221F8@mail.kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v5.10-rc2
for you to fetch changes up to cf1ad559a20d1930aa7b47a52f54e1f8718de301:
regulator: defer probe when trying to get voltage from unresolved supply (2020-11-03 13:19:01 +0000)
----------------------------------------------------------------
regulator: Fixes for v5.10
An addition to MAINTAINERS plus a fix for a nasty bootstrapping problem
which caused problems when we need to read the voltage of a regulator
that is not yet available during initialization, we were not correctly
distinguishing between this case and the case where a regulator is put
into a bypass mode.
----------------------------------------------------------------
Mark Brown (1):
Merge tag 'v5.10-rc1' into regulator-5.10
Michał Mirosław (1):
regulator: defer probe when trying to get voltage from unresolved supply
Robert Marko (1):
MAINTAINERS: Add entry for Qualcomm IPQ4019 VQMMC regulator
MAINTAINERS | 8 ++++++++
drivers/regulator/core.c | 2 ++
2 files changed, 10 insertions(+)
next reply other threads:[~2020-11-05 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 16:45 Mark Brown [this message]
2020-11-05 20:21 ` [GIT PULL] regulator fixes for v5.10-rc2 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=20201105164547.AE3AD221F8@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