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 v6.14-merge-window
Date: Wed, 29 Jan 2025 13:23:27 +0000	[thread overview]
Message-ID: <09df24e539a2259c800a02d49557f34e.broonie@kernel.org> (raw)

The following changes since commit 367a8200a91025289f9664e468fbc2b67c95e70e:

  regulator: dt-bindings: Add regulator-power-budget-milliwatt property (2025-01-17 17:48:55 +0000)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.14-merge-window

for you to fetch changes up to 155c569fa4c3b340fbf8571a0e42dd415c025377:

  regulator: core: Add missing newline character (2025-01-22 14:29:29 +0000)

----------------------------------------------------------------
regulator: Fixes for v6.14

A couple of fixes that have come in during the merge window, one that
operates the TPS6287x devices more within the design spec and can
prevent current surges when changing voltages and another more trivial
one for error message formatting.

----------------------------------------------------------------
Alexander Stein (1):
      regulator: core: Add missing newline character

Jonas Andreasson (1):
      regulator: TPS6287X: Use min/max uV to get VRANGE

 drivers/regulator/core.c               |  2 +-
 drivers/regulator/tps6287x-regulator.c | 57 ++++++++++++++++++++++++++++++++++
 2 files changed, 58 insertions(+), 1 deletion(-)

             reply	other threads:[~2025-01-29 13:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-29 13:23 Mark Brown [this message]
2025-01-29 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=09df24e539a2259c800a02d49557f34e.broonie@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®