From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-s390 <linux-s390@vger.kernel.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>
Subject: Re: [GIT PULL] s390 patches for 4.19 #3
Date: Fri, 14 Sep 2018 07:37:56 +0200 [thread overview]
Message-ID: <20180914073756.2c208e55@mschwideX1> (raw)
In-Reply-To: <CA+55aFxYR__1rfT--Vxkoh1RyA+g6pQs87H8tk7ajXW9L8p7tg@mail.gmail.com>
On Thu, 13 Sep 2018 16:26:38 -1000
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Sep 13, 2018 at 2:02 AM Martin Schwidefsky
> <schwidefsky@de.ibm.com> wrote:
> >
> > this is the first try to do a pull request for s390 with a signed tag.
> > I keep my fingers crossed that the setup works as intended.
> >
> > I have used the 8A8FDAE0 signing sub-key of my 26AE5DD2 master key:
>
> The signed tag looks ok, but you haven't actually pushed out your new
> signing sub-key to the keyservers, so I can't actually verify it.
>
> So a "gpg --send-key" would be a good idea.
I did push it to keys.gnupg.net, but the sub-key is brand new and
probably takes some time to sync on the key server network.
The key is there on pgp.mit.edu this morning, it that to one you
are using or do you prefer a different one?
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2018-09-14 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-13 12:01 [GIT PULL] s390 patches for 4.19 #3 Martin Schwidefsky
2018-09-14 2:26 ` Linus Torvalds
2018-09-14 5:37 ` Martin Schwidefsky [this message]
2018-09-14 5:42 ` Linus Torvalds
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=20180914073756.2c208e55@mschwideX1 \
--to=schwidefsky@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).