From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel <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 the 4.17 merge window #1
Date: Mon, 9 Apr 2018 18:22:33 +0200 [thread overview]
Message-ID: <20180409182233.5a9150c5@mschwideX1> (raw)
In-Reply-To: <CAADWXX-188FC4aBjYMaRwrhcUNvoazwZSirPX3Y2P8PuFiV0bQ@mail.gmail.com>
On Mon, 9 Apr 2018 09:07:12 -0700
Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Mon, Apr 9, 2018 at 6:18 AM, Martin Schwidefsky
> <schwidefsky@de.ibm.com> wrote:
> > Hi Linus,
> >
> > On Tue, 3 Apr 2018 11:12:42 +0200
> > Martin Schwidefsky <schwidefsky@de.ibm.com> wrote:
> >
> >> please pull from the 'for-linus' branch of
> >>
> >> git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux.git for-linus
> >>
> >> to receive the following updates:
> >
> > Ping.
> >
> > Did this please-pull get lost or is there a deeper reason that prevents
> > the upstream integration?
>
> I'm not finding the original at all, and this 'ping' message I found
> in my spam-box. Maybe the original was marked as spam too and I didn't
> notice, and it got deleted with the other spam.
Not good, any idea why the ping message has been marked as spam?
Maybe there is something in the headers that gives a hint.
> Anyway, pulled now (even if this ping didn't have the diffstat and
> shortlog to check against - everything looks sane)
Thanks.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2018-04-09 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 9:12 Martin Schwidefsky
2018-04-09 13:18 ` Martin Schwidefsky
2018-04-09 16:07 ` Linus Torvalds
2018-04-09 16:22 ` Martin Schwidefsky [this message]
2018-04-09 16:40 ` 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=20180409182233.5a9150c5@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
all inboxes | Powered by JetHome®