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.16-rc4
Date: Fri, 04 Jul 2025 16:06:59 +0100 [thread overview]
Message-ID: <29572e6de29cb03ebdf8b553a11a800e.broonie@kernel.org> (raw)
The following changes since commit d0b3b7b22dfa1f4b515fd3a295b3fd958f9e81af:
Linux 6.16-rc4 (2025-06-29 13:09:04 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v6.16-rc4
for you to fetch changes up to c9764fd88bc744592b0604ccb6b6fc1a5f76b4e3:
regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods (2025-07-03 12:22:35 +0100)
----------------------------------------------------------------
regulator: Fixes for v6.16
A few driver fixes (the GPIO one being potentially nasty, though it has
been there for a while without anyone reporting it), and one core fix
for the rarely used combination of coupled regulators and unbinding.
----------------------------------------------------------------
Alessandro Carminati (1):
regulator: core: fix NULL dereference on unbind due to stale coupling data
Jisheng Zhang (2):
regulator: sy8824x: Fix ID table driver_data
regulator: mp886x: Fix ID table driver_data
Manivannan Sadhasivam (1):
regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods
Shree Ramamoorthy (1):
regulator: tps65219: Fix devm_kmalloc size allocation
drivers/regulator/core.c | 1 +
drivers/regulator/gpio-regulator.c | 8 ++++----
drivers/regulator/mp886x.c | 3 ++-
drivers/regulator/sy8824x.c | 5 ++++-
drivers/regulator/tps65219-regulator.c | 28 ++++++++++++++--------------
5 files changed, 25 insertions(+), 20 deletions(-)
next reply other threads:[~2025-07-04 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-04 15:06 Mark Brown [this message]
2025-07-04 17:36 ` 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=29572e6de29cb03ebdf8b553a11a800e.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®