From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-spi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] spi updates for v5.2
Date: Tue, 7 May 2019 20:03:45 +0900 [thread overview]
Message-ID: <20190507110345.GF14916@sirena.org.uk> (raw)
In-Reply-To: <CAHk-=wi4EJQLoMNd4ptiiZvLy8ZW49pcCy0VQwZt4xhDDqSOjw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 834 bytes --]
On Mon, May 06, 2019 at 08:13:49PM -0700, Linus Torvalds wrote:
> On Mon, May 6, 2019 at 8:02 PM Mark Brown <broonie@kernel.org> wrote:
> > Everything I'm
> > seeing is saying that Google just isn't enthusiastic about domains like
> > kernel.org which is going an issue.
> Well, there are other people who use kernel.org email addresses. Ingo
> Molnar, Rafael Wysocki, a couple of others. But you're the one
> getting marked as spam.
I'm not going to search for rule 36 SPI.
> Somebody just hates you. I do end up checking my spam-box regularly,
> so maybe it doesn't matter.
Some spot checks are suggesting that they use gmail as their outbound
relay which I can imagine they'd like but would break some stuff for me
for non-kernel.org mail I think, it'd be a major rework to not inject
stuff via sendmail.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-05-07 11:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:33 [GIT PULL] spi updates for v5.2 Mark Brown
2019-05-06 19:01 ` Linus Torvalds
2019-05-07 2:18 ` Mark Brown
2019-05-07 2:34 ` Linus Torvalds
2019-05-07 3:09 ` Mark Brown
2019-05-07 3:02 ` Mark Brown
2019-05-07 3:13 ` Linus Torvalds
2019-05-07 11:03 ` Mark Brown [this message]
2019-05-07 12:07 ` Sebastian Reichel
2019-05-08 6:09 ` Mark Brown
2019-05-08 10:13 ` Sebastian Reichel
2019-05-08 10:27 ` Mark Brown
2019-05-08 10:20 ` Brian Masney
2019-05-07 15:08 ` Linus Torvalds
2019-05-08 6:11 ` Mark Brown
2019-05-07 15:10 ` 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:
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=20190507110345.GF14916@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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).