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.0-merge-window
Date: Fri, 20 Feb 2026 19:09:51 +0000 [thread overview]
Message-ID: <8179f730937cbdbefa2e604dfd26cd30@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
The following changes since commit 914809c666d6c96d130da4755daa5bb0a57f0e12:
Samsung S2MPG10 regulator and S2MPG11 PMIC drivers (2026-02-05 00:07:58 +0000)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.0-merge-window
for you to fetch changes up to 09ad01a530bb6ad260bda4fa56bab84619d90968:
regulator: s2mps11: fix pctrlsel macro usage in s2mpg10_of_parse_cb() (2026-02-16 16:30:47 +0000)
----------------------------------------------------------------
regulator: Fixes from the v7.0 merge window
A few driver specific fixes, plus a patch from Bjorn which removes a
fixed limit on regulator names that was breaking some Qualcomm systems.
----------------------------------------------------------------
Adam Ford (1):
regulator: mt6363: Fix interrmittent timeout
André Draszik (2):
regulator: s2mps11: drop redundant sanity checks in s2mpg10_of_parse_cb()
regulator: s2mps11: fix pctrlsel macro usage in s2mpg10_of_parse_cb()
Bjorn Andersson (1):
regulator: core: Remove regulator supply_name length limit
drivers/regulator/core.c | 12 +-----------
drivers/regulator/mt6363-regulator.c | 9 ++++++++-
drivers/regulator/s2mps11.c | 22 +++++++++-------------
3 files changed, 18 insertions(+), 25 deletions(-)
next reply other threads:[~2026-02-20 19:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 19:09 Mark Brown [this message]
2026-02-21 1:20 ` [GIT PULL] regulator fixes for v7.0-merge-window 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=8179f730937cbdbefa2e604dfd26cd30@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.