From: bcain@codeaurora.org
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-hexagon <linux-hexagon@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
sidneym@codeaurora.org,
clang-built-linux <clang-built-linux@googlegroups.com>
Subject: Re: [GIT PULL] hexagon changes for v5.13
Date: Thu, 06 May 2021 11:17:56 -0500 [thread overview]
Message-ID: <43df6483efd78b46f53e865bd75d75a4@codeaurora.org> (raw)
In-Reply-To: <81ecc015b1bd773f583cc86490e392a0@codeaurora.org>
On 2021-05-06 11:16, bcain@codeaurora.org wrote:
> On 2021-05-06 11:03, Linus Torvalds wrote:
>> On Wed, May 5, 2021 at 2:10 PM <bcain@codeaurora.org> wrote:
>>>
>>> Please pull the following changes for Hexagon: they contain build
>>> fixes.
>>
>> The pull looks fine, but I'm wondering what key you've signed this
>> with?
>>
>> I find your key 175C464E541B6D47 in the kernel.org pgpkeys archive,
>> but your tag was signed with RSA key 1A54AFB8E5646C32, which I don't
>> find.
>>
>> And the standard keyservers are - as usual - not very helpful.
>
> I apologize -- in my initial account setup I'd done the key creation
> without a signing feature/capability. So in order to sign the tag I
> realized I needed a new subkey for signing. I tried broadcasting the
> new key but perhaps I did not send it correctly. I'll try it again
> today.
>
> http://keyserver.ubuntu.com/pks/lookup?search=bcain&fingerprint=on&op=index
>
> ^^^ this shows one that has 3d66aae474594824c88ce0f81a54afb8e5646c32
> but I'm not quite sure if this is a good keyserver or not.
Oh, but the new signing subkey has not been signed by anyone yet. I
will see about that.
-Brian
next prev parent reply other threads:[~2021-05-06 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-05 21:09 [GIT PULL] hexagon changes for v5.13 bcain
2021-05-06 16:03 ` Linus Torvalds
2021-05-06 16:16 ` bcain
2021-05-06 16:17 ` bcain [this message]
2021-05-06 16:52 ` Linus Torvalds
2021-05-06 16:35 ` 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=43df6483efd78b46f53e865bd75d75a4@codeaurora.org \
--to=bcain@codeaurora.org \
--cc=clang-built-linux@googlegroups.com \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sidneym@codeaurora.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