All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] spi updates for v5.2
Date: Mon, 6 May 2019 19:34:29 -0700	[thread overview]
Message-ID: <CAHk-=whLZMe5kNpNMnhh5oVHFKNv7Um4tBS+rH=kLvM+CWzzxw@mail.gmail.com> (raw)
In-Reply-To: <20190507021853.GY14916@sirena.org.uk>

On Mon, May 6, 2019 at 7:19 PM Mark Brown <broonie@kernel.org> wrote:
> >
> >     dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org
>
> That looks like it's a fail on validation of the kernel.org bit of
> things which I have no control over and which purposely doesn't
> advertise DKIM stuff in the hope that people will actually be able to
> send mail from non-kernel.org mail servers.

Looking around, I think you're right, and it's probably not actually
the DKIM thing that causes problems.

Because yes, kernel.org dmarc will just say "ignore".

So I think it's just google that still doesn't like sirena.org.uk.
Iirc, that's happened before, no?

                   Linus

  reply	other threads:[~2019-05-07  2:34 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 [this message]
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
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='CAHk-=whLZMe5kNpNMnhh5oVHFKNv7Um4tBS+rH=kLvM+CWzzxw@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.