From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: updates for 4.11
Date: Wed, 22 Feb 2017 18:04:47 +0000 [thread overview]
Message-ID: <20170222180446.GO27510@arm.com> (raw)
In-Reply-To: <CAADWXX_gu1cQmTa_dyf7D_56zGmindPVW2V6OZYOpu28A=aAmA@mail.gmail.com>
On Wed, Feb 22, 2017 at 09:10:14AM -0800, Linus Torvalds wrote:
> On Wed, Feb 22, 2017 at 8:28 AM, Will Deacon <will.deacon@arm.com> wrote:
> >
> > Please pull the following arm64 updates for 4.11. The summary is in the
> > tag below.
>
> Hmm. This was marked as spam for me. No idea why, it wasn't for any
> SPF or DKIM problems. Google just said "looks like other mail marked
> as spam".
>
> Anyway, I obviously caught it in my spambox, so no worries. Just a
> heads-up that gmail has you in its sights..
Thanks for letting me know. Our SMTP server had some issues last week
that resulted in it appearing on some blacklists, but that should have
been resolved by now.
Maybe it's just the way I write these things :/
Will
P.S. Congratulations on your PRIZE!!!
prev parent reply other threads:[~2017-02-22 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 16:28 [GIT PULL] arm64: updates for 4.11 Will Deacon
2017-02-22 17:10 ` Linus Torvalds
2017-02-22 18:04 ` Will Deacon [this message]
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=20170222180446.GO27510@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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