From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Yehezkel Bernat <YehezkelShB@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Lukas Wunner <lukas@wunner.de>,
Andreas Noever <andreas.noever@gmail.com>,
linux-usb@vger.kernel.org
Subject: Re: [GIT PULL] Thunderbolt/USB4 changes for v5.18 merge window
Date: Fri, 11 Mar 2022 16:54:20 +0200 [thread overview]
Message-ID: <YitinFevmtz9fB32@lahna> (raw)
In-Reply-To: <YitSc/Sy8O4BSilF@lahna>
Hi Greg,
On Fri, Mar 11, 2022 at 03:45:39PM +0200, Mika Westerberg wrote:
> On Fri, Mar 11, 2022 at 12:46:01PM +0100, Greg Kroah-Hartman wrote:
> > On Tue, Mar 08, 2022 at 02:20:33PM +0200, Mika Westerberg wrote:
> > > Hi Greg,
> > >
> > > The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
> > >
> > > Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
> > >
> > > are available in the Git repository at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/westeri/thunderbolt.git tags/thunderbolt-for-v5.18-rc1
> >
> > The gpg key you used to sign this tag is expired, so my checks fail :(
>
> Hmm,
>
> I extended the expiration time already last year and it shows here:
>
> rsa4096 2017-11-02 [SC] [expires: 2022-08-23]
>
> For that key. I pushed it to the keyserver too at the time
> (keyserver.ubuntu.com).
>
> > Please fix this.
>
> Sure but how? :)
I just read this:
https://korg.docs.kernel.org/pgpkeys.html
and uploaded the updated key to https://keys.openpgp.org/upload/ too. I
hope it works now. Sorry about the mess.
prev parent reply other threads:[~2022-03-11 14:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 12:20 [GIT PULL] Thunderbolt/USB4 changes for v5.18 merge window Mika Westerberg
2022-03-11 11:46 ` Greg Kroah-Hartman
2022-03-11 13:45 ` Mika Westerberg
2022-03-11 14:50 ` Greg Kroah-Hartman
2022-03-11 14:54 ` Mika Westerberg [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=YitinFevmtz9fB32@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=michael.jamet@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).