Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sun, 25 Aug 2019 18:35:38 -0400
From:   Sasha Levin <sashal@kernel.org>
To:     =?iso-8859-1?Q?J=F6rg-Volker?= Peetz <jvpeetz@web.de>
Cc:     stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 5.2.10
Message-ID: <20190825223537.GB5281@sasha-vm>
References: <20190825144703.6518-1-sashal@kernel.org>
 <qju9bd$47qi$1@blaine.gmane.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <qju9bd$47qi$1@blaine.gmane.org>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Thanks for looking into this!

On Sun, Aug 25, 2019 at 05:26:37PM +0200, J?rg-Volker Peetz wrote:
>Where can I find your public gpg key and it's fingerprint?
>It's not yet documented on https://www.kernel.org/category/signatures.html .

You're right, I'll send a patch to add my fingerprint as well.

>I'm asking because the "gpg --locate-keys" method does not work for me.

I can confirm this, and this is weird... I see a kernel.org UID on the
key, and gpg seems to confirm that as well:

$ gpg --quick-add-uid DEA66FF797772CDC 'Sasha Levin <sashal@kernel.org>'
gpg: Such a user ID already exists on this key!

Let me contact kernel.org support to see what I'm doing wrong...

--
Thanks,
Sasha