mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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-rc4
Date: Sun, 26 Jul 2026 17:05:21 +0100	[thread overview]
Message-ID: <5bfdeeaf106a7a913edd36e9ef9ca02c@kernel.org> (raw)

The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:

  Linux 7.2-rc4 (2026-07-19 13:54:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.2-rc4

for you to fetch changes up to a45cc646a3aa83eb4ab4c7ed2685785ea51dc5e6:

  regulator: core: clamp voltage constraints before applying apply_uV (2026-07-21 22:35:08 +0100)

----------------------------------------------------------------
regulator: Fixes for v7.2

One driver specific fix where one of the MediaTek drivers duplicated
some core code buggily, and a core fix for an ordering issue on startup
where we could end up configuring a voltage outside of constraints due
to the order in which we applied constraints.

----------------------------------------------------------------
Daniel Golle (1):
      regulator: mt6358: use regmap helper to read fixed LDO calibration

Kamal Wadhwa (1):
      regulator: core: clamp voltage constraints before applying apply_uV

 drivers/regulator/core.c             | 163 +++++++++++++++++++----------------
 drivers/regulator/mt6358-regulator.c |   2 +-
 2 files changed, 91 insertions(+), 74 deletions(-)

             reply	other threads:[~2026-07-26 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-26 16:05 Mark Brown [this message]
2026-07-26 20:00 ` pr-tracker-bot
2026-07-26 20:00 ` 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=5bfdeeaf106a7a913edd36e9ef9ca02c@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

all inboxes | Powered by JetHome®