From: "Uwe Kleine-König" <ukleinek@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: users@linux.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
lpcosse-keysigning@baylibre.com
Subject: Re: PGP keysigning at LPC/OSSE 2026 (Reminder for registration)
Date: Sun, 20 Sep 2026 12:10:15 +0200 [thread overview]
Message-ID: <aq-wN34RCBNCRGK8@monoceros> (raw)
In-Reply-To: <CAMuHMdXXVabVQq9Y_H3NKWTHciBuqZmkzrr78wGMi76DBZoVoQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1240 bytes --]
Hello Geert,
On Sun, Sep 20, 2026 at 10:35:36AM +0200, Geert Uytterhoeven wrote:
> On Tue, 15 Sept 2026 at 10:25, Uwe Kleine-König <ukleinek@kernel.org> wrote:
> > this is a reminder for the PGP keysigning event held during Linux
> > Plumbers and Open Source Summit Europe in Prague this October.
>
> Thanks for organizing!
>
> > While it's not mandatory, it will speed up and simplify the processes if
> > you register with your certificate for the event. Please do so by
> > sending your public key to lpcosse-keysigning@baylibre.com until
> > 2026-09-27 08:00 UTC. If you saw the initial announcement[1] and thought
> > it was still to early and I'm on vacation, please hit reply now and
> > attach (or include inline) your certificate which can probably be
> > generated using:
> >
> > gpg --export --armor your-email-address@example.com
>
> Note that this would include all your expired/revokes keys (if any),
> so you may want to specify the key ID instead.
That's right, and that's why I wrote "probably" above. So if you're
unsure, check the output of
gpg --list-key $whatever
to match what you intend to send and only then do
gpg --export --armor $whatever
.
Best regards
Uwe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-09-20 10:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 8:16 Uwe Kleine-König
2026-09-20 8:35 ` Geert Uytterhoeven
2026-09-20 10:10 ` Uwe Kleine-König [this message]
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=aq-wN34RCBNCRGK8@monoceros \
--to=ukleinek@kernel.org \
--cc=geert@linux-m68k.org \
--cc=konstantin@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lpcosse-keysigning@baylibre.com \
--cc=users@linux.kernel.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®