[GIT PULL] regulator fixes for v7.3-rc6

[GIT PULL] regulator fixes for v7.3-rc6

[Mark Brown]

The following changes since commit 72d3fcf802c45d00b300f25b848a93c3a2bd7c7e:

  Linux 7.3-rc5 (2026-09-27 13:55:01 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 28c2388ee24cdbefbcc458fa41ef7bffaaa1cc83:

  regulator: ltc3676: don't read the write-only HRST and CLIRQ registers (2026-10-06 17:59:42 +0200)

----------------------------------------------------------------
regulator: Fixes for v7.3

There's a couple of core fixes here, there were a couple of issues with
of_regulator_bulk_get_all() not behaving consistently with the other
bulk regulator APIs which caused memory leaks and error handling issues
in users.  We also have a of fairly standard driver specific fixes.

----------------------------------------------------------------
Abhishek Ojha (1):
      regulator: ltc3676: don't read the write-only HRST and CLIRQ registers

Alexey Charkov (2):
      regulator: of: fill in supply names in of_regulator_bulk_get_all()
      regulator: of: state who owns the array from of_regulator_bulk_get_all()

Mark Brown (1):
      regulator: of: Fixes to of_regulator_bulk_get_all()

Ridham Khurana (1):
      regulator: tps6594-regulator: Fix n_linear_ranges for TPS65224 BUCK2-4

 drivers/regulator/ltc3676.c           | 15 ++++++++++++---
 drivers/regulator/of_regulator.c      | 29 ++++++++++++++++++++++-------
 drivers/regulator/tps6594-regulator.c |  6 +++---
 3 files changed, 37 insertions(+), 13 deletions(-)

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Linus Torvalds]

On Sat, 10 Oct 2026 at 16:48, Mark Brown <broonie@kernel.org> wrote:
>
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.3-rc6

I don't recognize the signing key this was done with - and it also
doesn't match anything from the kernel.org pgp key repository.

Both of your recent pull requests used that unknown key. I'm holding
off for now.

                Linus

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Sasha Levin]

On Sat, Oct 10, 2026 at 05:06:37PM -0700, Linus Torvalds wrote:
>On Sat, 10 Oct 2026 at 16:48, Mark Brown <broonie@kernel.org> wrote:
>>
>>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.3-rc6
>
>I don't recognize the signing key this was done with - and it also
>doesn't match anything from the kernel.org pgp key repository.
>
>Both of your recent pull requests used that unknown key. I'm holding
>off for now.

I noticed this key change with Mark's linux-next releases, so I looked into it:
looks like the key was sent in
https://lore.kernel.org/keys/31c98cd5-bea4-428c-950f-d38a43709245@sirena.org.uk/
but not updated in the kernel.org repo just yet. It seemed to be a new properly
signed subkey.

-- 
Thanks,
Sasha

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Linus Torvalds]

On Sun, 11 Oct 2026 at 06:27, Sasha Levin <sashal@kernel.org> wrote:
>
> I noticed this key change with Mark's linux-next releases, so I looked into it:
> looks like the key was sent in
> https://lore.kernel.org/keys/31c98cd5-bea4-428c-950f-d38a43709245@sirena.org.uk/
> but not updated in the kernel.org repo just yet. It seemed to be a new properly
> signed subkey.

Bah. It's not like I need reminding about how much I dislike pgp, but
this whole "people change their keys without giving a reason or
telling me" is something that *should* change, and doesn't require
fixing that horrible program.

PLEASE, people. Don't just throw your keys out into the wild blue
yonder and then assume that's it. The people who *care* about your
keys should be told about it, and why you suddenly changed your key.

And if the "suddenly changed your key" is due to something truly
idiotic like "I made the expiration be really short", then you should
fix your evil ways. Pgp key expirations are almost entirely pointless,
and they turn from pointless to actively stupid when you then don't
inform people about them and abotu the new keys.

This wouldn't be an issue in a perfect world where pgp key updates
work sanely, but that is not the world we live in.

              Linus

Re: [GIT PULL] regulator fixes for v7.3-rc6

[pr-tracker-bot]

The pull request you sent on Sun, 11 Oct 2026 00:48:12 +0100:

> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v7.3-rc6

has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/5906f156e8818d29839d7d7280b691f627b59883

Thank you!

-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

On Sun, Oct 11, 2026 at 11:27:51AM -0700, Linus Torvalds wrote:

> Bah. It's not like I need reminding about how much I dislike pgp, but
> this whole "people change their keys without giving a reason or
> telling me" is something that *should* change, and doesn't require
> fixing that horrible program.

> PLEASE, people. Don't just throw your keys out into the wild blue
> yonder and then assume that's it. The people who *care* about your
> keys should be told about it, and why you suddenly changed your key.

Sorry, I was under the impression that the keyring you were using was
tied in with the kernel.org keyring and didn't realise that you needed
notifying separately.  This is me adding new subkeys to my existing key
so that I have backups of them and am not stuck with the single
smartcard I generated subkeys on 10 years or so ago and can also have a
physical token I can plug into USB C ports.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Linus Torvalds]

On Mon, 12 Oct 2026 at 06:29, Mark Brown <broonie@kernel.org> wrote:
>
> Sorry, I was under the impression that the keyring you were using was
> tied in with the kernel.org keyring

It is. Not automatically - but when I see missing keys, the first
thing I do is check the kernel.org repo.

But your new key had not actually shown up there. I don't know what
the latency for it normally is, but I think it's all "entirely manual,
random when it gets updated".

Right now the last update to your key on kernel.org is from July, and
that looks like it was just an automated "update signatures" kind of
thing, not actual new key data.

           Linus

Re: [GIT PULL] regulator fixes for v7.3-rc6

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Mon, Oct 12, 2026 at 10:24:56AM -0700, Linus Torvalds wrote:
> On Mon, 12 Oct 2026 at 06:29, Mark Brown <broonie@kernel.org> wrote:

> > Sorry, I was under the impression that the keyring you were using was
> > tied in with the kernel.org keyring

> It is. Not automatically - but when I see missing keys, the first
> thing I do is check the kernel.org repo.

> But your new key had not actually shown up there. I don't know what
> the latency for it normally is, but I think it's all "entirely manual,
> random when it gets updated".

> Right now the last update to your key on kernel.org is from July, and
> that looks like it was just an automated "update signatures" kind of
> thing, not actual new key data.

Yeah, that one was nothing to do with me AFAIK so will have been pulling
sigs.  I'll file a ticket to helpdesk asking for the process to be more
chatty about what's going on to try to avoid surprises and so people
know when the updates are live, I got a "your message is held" then saw
the update had gone through on the list.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]