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.10-rc4
Date: Sat, 22 Jun 2024 17:27:24 +0100 [thread overview]
Message-ID: <f91a2271e0971d201278b80773b6a6b4.broonie@kernel.org> (raw)
The following changes since commit c3f38fa61af77b49866b006939479069cd451173:
Linux 6.10-rc2 (2024-06-02 15:44:56 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.10-rc4
for you to fetch changes up to 0057222c45140830a7bf55e92fb67f84a2814f67:
regulator: axp20x: AXP717: fix LDO supply rails and off-by-ones (2024-06-12 21:30:43 +0100)
----------------------------------------------------------------
regulator: Fixes for v6.10
A few driver specific fixes for incorrect device descriptions, plus a
fix for a missing symbol export which causes build failures for some
newly added drivers in other trees.
----------------------------------------------------------------
Andre Przywara (1):
regulator: axp20x: AXP717: fix LDO supply rails and off-by-ones
Biju Das (1):
regulator: core: Fix modpost error "regulator_get_regmap" undefined
Kalle Niemi (1):
regulator: bd71815: fix ramp values
Thomas Richard (1):
regulator: tps6594-regulator: Fix the number of irqs for TPS65224 and TPS6594
drivers/regulator/axp20x-regulator.c | 33 +++++++++++++++++++--------------
drivers/regulator/bd71815-regulator.c | 2 +-
drivers/regulator/core.c | 1 +
drivers/regulator/tps6594-regulator.c | 12 ++++--------
4 files changed, 25 insertions(+), 23 deletions(-)
next reply other threads:[~2024-06-22 16:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 16:27 Mark Brown [this message]
2024-06-22 21:05 ` 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=f91a2271e0971d201278b80773b6a6b4.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®