From: Linus Torvalds <torvalds@linux-foundation.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Duc Dang <dhdang@apm.com>,
linaro-acpi@lists.linaro.org, lkml <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Lv Zheng <lv.zheng@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2] PCI: Add information about describing PCI in ACPI
Date: Tue, 29 Nov 2016 15:39:11 -0800 [thread overview]
Message-ID: <CAADWXX_ipJ+pVmV5s2oLCKBrC5qUDASOZf=tpBfJWELExam+hQ@mail.gmail.com> (raw)
In-Reply-To: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com>
Bjorn, this email was marked as spam, because:
It has a from address in google.com but has failed google.com's
required tests for authentication
in particular, it looks like you used a non-google smtp server
(kernel.org) to send the email, so there is no DKIM hash (or perhaps
google just uses some other non-standard marker for "this actually
came from google"). So gmail marks it as spam because dmarc fails:
dmarc=fail (p=REJECT dis=NONE) header.from=google.com
Just to let you know. If you use your google.com email, you do need to
go through the google smtp server.
This may or may not be new - I didn't go and look at old messages of
yours, but it is possible that google.com enabled dmarc/dkim recently.
Linus
On Tue, Nov 29, 2016 at 1:39 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> Here's another stab at this writeup. I'd appreciate any comments!
next prev parent reply other threads:[~2016-11-29 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 21:39 [PATCH v2] PCI: Add information about describing PCI in ACPI Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-12-13 9:09 ` Jon Masters
2017-02-01 16:50 ` Bjorn Helgaas
2016-11-29 23:39 ` Linus Torvalds [this message]
2016-11-30 16:17 ` Bjorn Helgaas
2016-12-01 22:36 ` Bjorn Helgaas
2016-12-01 22:37 ` Rafael J. Wysocki
2016-12-01 23:27 ` Bjorn Helgaas
2016-12-02 0:28 ` Rafael J. Wysocki
2016-12-02 2:18 ` Bjorn Helgaas
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='CAADWXX_ipJ+pVmV5s2oLCKBrC5qUDASOZf=tpBfJWELExam+hQ@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--cc=dhdang@apm.com \
--cc=gabriele.paoloni@huawei.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lv.zheng@intel.com \
--cc=rafael@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 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).