regulator fixes for v5.3
The following changes since commit 5f9e832c137075045d15cd6899ab0505cfb2ca4b:
Linus 5.3-rc1 (2019-07-21 14:05:38 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v5.3-rc3
for you to fetch changes up to 811ba489fa524ec634933cdf83aaf6c007a4c004:
regulator: of: Add of_node_put() before return in function (2019-08-01 14:07:46 +0100)
----------------------------------------------------------------
regulator: Fixes for v5.3
A few small driver specific fixes here plus one core fix for a refcounting problem with DT which will have little practical impact unless overlays are used.
----------------------------------------------------------------
Axel Lin (1):
regulator: lp87565: Fix probe failure for "ti,lp87565"
Jernej Skrabec (2):
regulator: axp20x: fix DCDCA and DCDCD for AXP806
regulator: axp20x: fix DCDC5 and DCDC6 for AXP803Mark Brown (1):
Merge tag 'v5.3-rc1' into regulator-5.3
Nishka Dasgupta (1):
regulator: of: Add of_node_put() before return in function
drivers/regulator/axp20x-regulator.c | 10 +++++----- drivers/regulator/lp87565-regulator.c | 8 ++++---- drivers/regulator/of_regulator.c | 4 +++- 3 files changed, 12 insertions(+), 10 deletions(-)
Mark,
these got marked as spam once again, because
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org
and I think it's because you have
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=sirena.org.uk;
but then you have
From: Mark Brown <[email protected]>
so the DKIM signature is all correct, but it's correct for sirena.org.uk, not for the sender information..
Linus
On Mon, Aug 05, 2019 at 11:42:29AM -0700, Linus Torvalds wrote:
Adding Konstantin.
Quoted 7 lines
these got marked as spam once again, because
dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org
and I think it's because you have
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
Quoted 8 lines
d=sirena.org.uk;
but then you have
From: Mark Brown <[email protected]>
so the DKIM signature is all correct, but it's correct for sirena.org.uk, not for the sender information..
Well, AFAICT this is your mail provider deciding to impose their own requirements on things. (and for clarity it's only the From: that has kernel.org, the envelope sender has sirena.org.uk.)
The DKIM signature there says that the sirena.org.uk systems are asserting that they take responsibility for the headers they sign, this is true and says nothing about the content of those headers other than you can tell if they were modified since leaving sirena.org.uk. The DMARC check is a separate one based on the domain reported in the address, kernel.org has one which explicitly advertises having no policy and only filtering 1% of outbound mail so shouldn't really mean anything for processing. DMARC can flag that there has to be a DKIM signature from the domain in the headers but kernel.org doesn't do that.
We *do* have a SPF record for kernel.org which I think isn't helping since it flags all hosts as being SOFTFAIL (the last match is ~all) which is supposed to be something along the lines of accept but flag, I can see your provider deciding that spam is the appropriate tag there. As far as I can see that'd also flag mail sent by things like the patchwork tracker bot similarly (it sends from mail.kernel.org which isn't advertised as a sender).
I suspect Google will only be happy if I inject mail through them, possibly also if I filter kernel.org mail to redirect via kernel.org though that might still trip them up.
The pull request you sent on Mon, 5 Aug 2019 15:34:31 +0100:
The pull request you sent on Mon, 5 Aug 2019 15:34:31 +0100:
Quoted 1 line
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git tags/regulator-fix-v5.3-rc3
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/df9edcba0b1146da5e4a2d1921bbc10c1a2fb55d
Thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.wiki.kernel.org/userdoc/prtracker