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

[Linus Torvalds]

On Sun, 11 Oct 2026 at 06:27, Sasha Levin <sashal@xxxxxxxxxx> 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@xxxxxxxxxxxxx/
> 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