Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755037AbcK2XjZ (ORCPT ); Tue, 29 Nov 2016 18:39:25 -0500 Received: from mail-io0-f169.google.com ([209.85.223.169]:34949 "EHLO mail-io0-f169.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753585AbcK2XjN (ORCPT ); Tue, 29 Nov 2016 18:39:13 -0500 MIME-Version: 1.0 In-Reply-To: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com> References: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com> From: Linus Torvalds Date: Tue, 29 Nov 2016 15:39:11 -0800 Message-ID: Subject: Re: [PATCH v2] PCI: Add information about describing PCI in ACPI To: Bjorn Helgaas Cc: Linux PCI , Ard Biesheuvel , Gabriele Paoloni , "Rafael J. Wysocki" , Duc Dang , linaro-acpi@lists.linaro.org, lkml , ACPI Devel Maling List , Lorenzo Pieralisi , Lv Zheng , "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 891 Lines: 22 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 wrote: > Here's another stab at this writeup. I'd appreciate any comments!