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 v7.2-rc2
Date: Fri, 10 Jul 2026 21:50:31 +0100 [thread overview]
Message-ID: <a3ba30e6eac83e8f19d3afc4bd1f1a32@kernel.org> (raw)
The following changes since commit 8cdeaa50eae8dad34885515f62559ee83e7e8dda:
Linux 7.2-rc2 (2026-07-05 14:44:06 -1000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.2-rc2
for you to fetch changes up to d38f8bd771c4999b797d7074b348cf201414bd34:
regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK (2026-07-09 01:41:17 +0100)
----------------------------------------------------------------
regulator: Fixes for v7.2
A couple of straightforward fixes for device loading, plus a fix for the
core support for keeping multiple regulators with voltages close to each
other that was sadly introduced due to one of the more beautiful corners
of our API design.
----------------------------------------------------------------
Pengpeng Hou (2):
regulator: mt6316: add missing MODULE_DEVICE_TABLE()
regulator: mt6363: add missing MODULE_DEVICE_TABLE()
Timur Tabi (1):
regulator: core: regulator_lock_two() should test for EDEADLK not EDEADLOCK
drivers/regulator/core.c | 4 ++--
drivers/regulator/mt6316-regulator.c | 1 +
drivers/regulator/mt6363-regulator.c | 1 +
3 files changed, 4 insertions(+), 2 deletions(-)
next reply other threads:[~2026-07-10 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 20:50 Mark Brown [this message]
2026-07-11 3:08 ` [GIT PULL] regulator fixes for v7.2-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=a3ba30e6eac83e8f19d3afc4bd1f1a32@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