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;
MIME-Version: 1.0
References: <20180913140149.3c39485c@mschwideX1>
In-Reply-To: <20180913140149.3c39485c@mschwideX1>
From:   Linus Torvalds <torvalds@linux-foundation.org>
Date:   Thu, 13 Sep 2018 16:26:38 -1000
Message-ID: <CA+55aFxYR__1rfT--Vxkoh1RyA+g6pQs87H8tk7ajXW9L8p7tg@mail.gmail.com>
Subject: Re: [GIT PULL] s390 patches for 4.19 #3
To:     Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-s390 <linux-s390@vger.kernel.org>,
        Heiko Carstens <heiko.carstens@de.ibm.com>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.

              Linus