From: f.fainelli@gmail.com (Florian Fainelli)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/3] Add support for Broadcom OTP controller
Date: Mon, 24 Oct 2016 12:54:14 -0700 [thread overview]
Message-ID: <e34f01b6-a059-9988-0f93-e5adb82a5436@gmail.com> (raw)
In-Reply-To: <CAADWXX-43-k2K2T1V5MQMd0z0V502wf1syNHERPfvNstOJw-3A@mail.gmail.com>
On 10/24/2016 12:39 PM, Linus Torvalds wrote:
> On Mon, Oct 24, 2016 at 12:12 PM, Jonathan Richardson
> <jonathan.richardson@broadcom.com> wrote:
>> This patch set adds support for Broadcom's OTP controller found on chips such
>> as Cygnus and Stingray. A node has been added to the Cygnus dts.
>
> These patches fail DKIM and will thus be marked as spam for a lot of people.
>
> The usual reason tends to be that you use the wrong smtp server that
> doesn't add the right signature. That's happened before with
> broadcom.com addresses.
The older setup was using smtphost.broadcom.com which we have now
documented as being invalid, here Jonathan used gmail directly (since
that's our mail provider now):
Received: from lbrmn-lnxub108.corp.ad.broadcom.com ([216.31.219.19])
by smtp.gmail.com with ESMTPSA id
s89sm8325746qkl.44.2016.10.24.12.12.00
(version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128);
Mon, 24 Oct 2016 12:12:03 -0700 (PDT)
Is there something else we need to check? Here is what I read for the
cover-letter:
Authentication-Results: mx.google.com;
dkim=pass header.i=@broadcom.com;
spf=pass (google.com: domain of
bcm-kernel-feedback-list.pdl+bncbdh5xfvr4ydrbbn2xhaakgqed7hz4rq at broadcom.com
designates 2607:f8b0:400c:c08::247 as permitted sender)
smtp.mailfrom=bcm-kernel-feedback-list.pdl+bncBDH5XFVR4YDRBBN2XHAAKGQED7HZ4RQ at broadcom.com;
dmarc=pass (p=QUARANTINE dis=NONE) header.from=broadcom.com
--
Florian
next prev parent reply other threads:[~2016-10-24 19:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 19:12 [PATCH v1 0/3] Add support for Broadcom OTP controller Jonathan Richardson
2016-10-24 19:12 ` [PATCH v1 1/3] dt-bindings: Document Broadcom OTP controller driver Jonathan Richardson
2016-10-31 1:38 ` Rob Herring
2016-10-31 20:12 ` Jonathan Richardson
2016-10-24 19:12 ` [PATCH v1 2/3] nvmem: Add the " Jonathan Richardson
2016-10-31 14:23 ` Srinivas Kandagatla
2016-10-31 19:55 ` Scott Branden
2016-10-31 20:38 ` Florian Fainelli
2016-10-24 19:12 ` [PATCH v1 3/3] ARM: dts: Add node for " Jonathan Richardson
2016-11-16 20:51 ` Florian Fainelli
2016-10-24 19:39 ` [PATCH v1 0/3] Add support for Broadcom OTP controller Linus Torvalds
2016-10-24 19:54 ` Florian Fainelli [this message]
2016-10-24 20:14 ` Linus Torvalds
2016-10-24 21:27 ` Florian Fainelli
2016-10-24 21:52 ` Linus Torvalds
2016-10-24 22:45 ` Markus Mayer
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=e34f01b6-a059-9988-0f93-e5adb82a5436@gmail.com \
--to=f.fainelli@gmail.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