From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sasha Levin <sashal@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] regulator fixes for v7.3-rc6
Date: Mon, 12 Oct 2026 18:38:52 +0100 [thread overview]
Message-ID: <51443ef4-fe92-423d-87f2-bfb543271f5f@sirena.org.uk> (raw)
In-Reply-To: <CAHk-=wionXXuNeBs80ECLud+N0s3yi1tyFsvvtfqO1S+1KQLSw@mail.gmail.com>
[-- 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 --]
next prev parent reply other threads:[~2026-10-12 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 23:48 Mark Brown
2026-10-11 0:06 ` Linus Torvalds
2026-10-11 13:26 ` Sasha Levin
2026-10-11 18:27 ` Linus Torvalds
2026-10-12 13:29 ` Mark Brown
2026-10-12 17:24 ` Linus Torvalds
2026-10-12 17:38 ` Mark Brown [this message]
2026-10-11 18:56 ` 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=51443ef4-fe92-423d-87f2-bfb543271f5f@sirena.org.uk \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@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®