LKML Archive on
help / color / mirror / Atom feed
From: Linus Torvalds <>
To: Yoshinori Sato <>
Cc: Linux Kernel Mailing List <>
Subject: Re: [GIT PULL] arch/h8300 update
Date: Wed, 22 Aug 2018 06:36:53 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Aug 22, 2018 at 5:47 AM Yoshinori Sato
<> wrote:
> I fixed it.



>   git:// tags/for-4.19

Sorry to be such a worry-wart, but that tag is signed by a key I've
never seen before.

It looks like you used some truly ancient key of yours for the signing
- the new tag is signed with this:

  1024D/DC21AAD1 2004-10-18

while the previous tags I have from you are signed with

  4096R/0B28399C 2015-06-25

and the two keys don't even have any shared signatures.

I *suspect* you've just changed machines and that your old key is your
real key, and the one for 2015 you created just for kernel signing and
you forgot about it.

And I've pulled the code, but I would ask that if  you have both keys
available, please at least cross-sign them with each other.



  reply	other threads:[~2018-08-22 13:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21  9:49 [GIT PULL] arch/h8300 update Yoshinori Sato
2018-08-21 20:33 ` Linus Torvalds
2018-08-22 12:48   ` Yoshinori Sato
2018-08-22 13:36     ` Linus Torvalds [this message]
2018-08-22 14:04       ` Linus Torvalds
2018-08-23 13:46         ` Yoshinori Sato
2019-01-05  9:34 Yoshinori Sato
2019-01-05 19:40 ` Linus Torvalds
2019-01-06 12:37   ` Yoshinori Sato
2019-01-05 20:20 ` pr-tracker-bot
2019-07-17  7:59 Yoshinori Sato
2019-07-17 16:37 ` Linus Torvalds
2019-07-17 16:50 ` 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).