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-rc7
Date: Fri, 14 Aug 2026 18:55:05 +0100	[thread overview]
Message-ID: <6f00328e664ccecf13d775034208f9aa@kernel.org> (raw)

The following changes since commit f5098b6bae761e346ebcd9da7f95622c04733cff:

  Linux 7.2-rc5 (2026-07-26 14:45:48 -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-rc7

for you to fetch changes up to 66694b5f90f3876fccb87bbd02b453cdc33b3ae4:

  regulator: fp9931: Fix VPOS/VNEG voltage selector table (2026-07-31 18:40:28 +0100)

----------------------------------------------------------------
regulator: Final changes for v7.2

There's one fix here for a data entry error in the voltage mapping in
the fp9931 driver, and a device ID addition for a LDO in the Qualcomm
PM8350b that's just a trivial quirk.

----------------------------------------------------------------
Esteban Urrutia (2):
      regulator: dt-bindings: qcom,rpmh: Add support for PM8350B
      regulator: qcom-rpmh: Add support for PM8350B

Mark Brown (1):
      regulator: PM8350B LDO support

Robby Cai (1):
      regulator: fp9931: Fix VPOS/VNEG voltage selector table

 .../bindings/regulator/qcom,rpmh-regulator.yaml    | 11 +++++
 drivers/regulator/fp9931.c                         | 54 +++++-----------------
 drivers/regulator/qcom-rpmh-regulator.c            |  9 ++++
 3 files changed, 32 insertions(+), 42 deletions(-)

             reply	other threads:[~2026-08-14 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 17:55 Mark Brown [this message]
2026-08-14 22:58 ` 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=6f00328e664ccecf13d775034208f9aa@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®