From: Greg KH <greg@kroah.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Sasha Levin <sashal@kernel.org>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
akpm@linux-foundation.org, jslaby@suse.cz, lwn@lwn.net
Subject: Re: Linux 5.2.10
Date: Mon, 26 Aug 2019 06:34:01 +0200 [thread overview]
Message-ID: <20190826043401.GC26547@kroah.com> (raw)
In-Reply-To: <dd3a1ec7d03888dade78db1e4c45ec1347c0815b.camel@tiscali.nl>
On Sun, Aug 25, 2019 at 07:33:36PM +0200, Paul Bolle wrote:
> Sasha,
>
> Sasha Levin schreef op zo 25-08-2019 om 10:47 [-0400]:
> > I'm announcing the release of the 5.2.10 kernel.
> >
> > All users of the 5.2 kernel series must upgrade.
> >
> > The updated 5.2.y git tree can be found at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-5.2.y
> > and can be browsed at the normal kernel.org git web browser:
> > https://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=summary
>
> v5.2.10 was tagged by sashal@kernel.org but signed by
> alexander.levin@verizon.com. Perhaps you could use one of gpg2's many options
> to add an
> aka "Sasha Levin <sashal@kernel.org>"
>
> line to that key. (I assume "--recv-key" then would have found your key.)
It's on that key already, have you refreshed your version of it?
thanks,
greg k-h
next prev parent reply other threads:[~2019-08-26 4:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-25 14:47 Linux 5.2.10 Sasha Levin
2019-08-25 14:47 ` Sasha Levin
2019-08-25 15:53 ` Bhaskar Chowdhury
2019-08-25 17:33 ` Paul Bolle
2019-08-26 4:34 ` Greg KH [this message]
2019-08-26 5:41 ` Bhaskar Chowdhury
2019-08-26 6:10 ` Greg KH
2019-08-26 7:55 ` Paul Bolle
[not found] ` <qju9bd$47qi$1@blaine.gmane.org>
2019-08-25 22:35 ` Sasha Levin
2019-08-26 4:33 ` Greg KH
2019-08-26 14:02 ` Jörg-Volker Peetz
2019-08-26 14:02 ` Jörg-Volker Peetz
2019-08-26 6:38 ` Bhaskar Chowdhury
2019-08-26 8:01 ` Greg KH
2019-08-26 8:21 ` Greg KH
2019-08-26 8:30 ` Bhaskar Chowdhury
2019-08-26 8:28 ` Bhaskar Chowdhury
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=20190826043401.GC26547@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=pebolle@tiscali.nl \
--cc=sashal@kernel.org \
--cc=stable@vger.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