[GIT PULL] regmap updates for v4.15

[GIT PULL] regmap updates for v4.15

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 2548 bytes --]

The following changes since commit 0b07194bb55ed836c2cc7c22e866b87a14681984:

  Linux 4.14-rc7 (2017-10-29 13:58:38 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.15

for you to fetch changes up to a15fdc340db10ac6f8d73e11f966f012a5e938a7:

  Merge remote-tracking branches 'regmap/topic/const' and 'regmap/topic/hwspinlock' into regmap-next (2017-11-06 11:39:41 +0000)

----------------------------------------------------------------
regmap: Updates for v4.15

After several quiet kernel releases we've got a couple of new features
in regmap, support for using hwspinlocks as the lock for the internal
data structures and a helper for polling on regmap_fields.  The Kconfig
dependencies on hwspinlocks were annoyingly difficult to squash between
things behaving surprisingly and randconfig, I could've squashed those
commits down but might've have caused hassle with other trees trying to
use the new support.

 - Support for using a hwspinlock to protect the regmap.
 - An iopoll style helper for regmap_field.

----------------------------------------------------------------
Arnd Bergmann (1):
      regmap: avoid -Wint-in-bool-context warning

Baolin Wang (2):
      regmap: Add hardware spinlock support
      regmap: Fix unused warning

Chen-Yu Tsai (1):
      regmap: add iopoll-like polling macro for regmap_field

Julia Lawall (1):
      regmap: constify regmap_bus structures

Mark Brown (8):
      Merge branch 'topic/namespace' of git://git.kernel.org/.../broonie/regmap into regmap-core
      Merge branch 'topic/field' of git://git.kernel.org/.../broonie/regmap into regmap-core
      regmap: Add a config option for hwspinlock
      regmap: Also protect hwspinlock in error handling path
      regmap: Clean up hwspinlock on regmap exit
      regmap: Try to work around Kconfig exploding on HWSPINLOCK
      Merge remote-tracking branch 'regmap/topic/core' into regmap-next
      Merge remote-tracking branches 'regmap/topic/const' and 'regmap/topic/hwspinlock' into regmap-next

Ramesh Shanmugasundaram (1):
      regmap: Avoid namespace collision within macro & tidy up

 drivers/base/regmap/Kconfig       |   4 ++
 drivers/base/regmap/internal.h    |   2 +
 drivers/base/regmap/regmap-spi.c  |   2 +-
 drivers/base/regmap/regmap-spmi.c |   4 +-
 drivers/base/regmap/regmap.c      | 111 ++++++++++++++++++++++++++++++++------
 include/linux/regmap.h            |  64 +++++++++++++++++++---
 6 files changed, 161 insertions(+), 26 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL] regmap updates for v4.15

[Linus Torvalds]

Mark,

On Mon, Nov 13, 2017 at 4:32 AM, Mark Brown <broonie@kernel.org> wrote:
>
>   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.15

All three of your pull requests were marked as spam by gmail.

I think it's the sirena.org.uk thing that triggers it, possibly made
worse by the fact that you then use a kernel.org email in your From:
line, so google thinks it's suspicious.

I'll add you explicitly as a contact, but if I see issues, others will too.

Don't ask me why gmail hates sirena.org.uk so much. I will point out
that the DNS is kind of odd: you obviously do have a MX record (and
gmail is happy with your DKIM), but you _only_ have a MX record for
sirena.org.uk, and regular name lookup takes you to some dodgy music
website (gigzmanagement.com - it's probably some "helpful" dns
provider money-making scheme where people pay to get non-taken DNS
placement).

Maybe that makes gmail say "dodgy site"? I do not know, and am just
throwing out possible random guesses.

             Linus

Re: [GIT PULL] regmap updates for v4.15

[Linus Torvalds]

On Mon, Nov 13, 2017 at 8:34 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> I'll add you explicitly as a contact, but if I see issues, others will too.

Oh, I had already done that, and gmail thought you were spam anyway.

You've really pissed off the email gods.

                  Linus

Re: [GIT PULL] regmap updates for v4.15

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 2299 bytes --]

On Mon, Nov 13, 2017 at 08:34:26AM -0800, Linus Torvalds wrote:
> On Mon, Nov 13, 2017 at 4:32 AM, Mark Brown <broonie@kernel.org> wrote:

> >   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v4.15

> All three of your pull requests were marked as spam by gmail.

> I think it's the sirena.org.uk thing that triggers it, possibly made
> worse by the fact that you then use a kernel.org email in your From:
> line, so google thinks it's suspicious.

> I'll add you explicitly as a contact, but if I see issues, others will too.

Yeah.  OTOH it's not like I don't frequently exchange mail with other
Google hosted accounts, it's possible they all have me listed as a
contact but that'd be surprising.

> Don't ask me why gmail hates sirena.org.uk so much. I will point out

Are you sure you're seeing stuff from sirena.org.uk and not
sirena.co.uk?  That's the envelope sender, I changed it after the last
time this happened to see if that helped.  The hosts it goes through are
still on .org.uk though.

> that the DNS is kind of odd: you obviously do have a MX record (and
> gmail is happy with your DKIM), but you _only_ have a MX record for
> sirena.org.uk, and regular name lookup takes you to some dodgy music
> website (gigzmanagement.com - it's probably some "helpful" dns
> provider money-making scheme where people pay to get non-taken DNS
> placement).

> Maybe that makes gmail say "dodgy site"? I do not know, and am just
> throwing out possible random guesses.

I've deleted that A record, hopefully that'll help.  It was something
that didn't get cleaned up in a previous hosting move.

The other thing I'm aware of is that SBL-CSS keeps continually listing
my outbound mail relay, unfortunately there's no way of finding out why
they're listing me, my guess has been that it's either that essentially
all my mail has different envelope and From senders or that someone is
explicitly flagging things (they have a good reputation and they don't
seem to be attempting to shake people down for money like some of the
other blacklists do).  Google might be looking at listings there, though
it doesn't seem to be listed right now so it's hard to tell.

Some of the SBL listings do seem to happen around the time I post to
the lists which does make me wonder.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL] regmap updates for v4.15

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

On Mon, Nov 13, 2017 at 05:16:14PM +0000, Mark Brown wrote:
> On Mon, Nov 13, 2017 at 08:34:26AM -0800, Linus Torvalds wrote:

> > Maybe that makes gmail say "dodgy site"? I do not know, and am just
> > throwing out possible random guesses.

> I've deleted that A record, hopefully that'll help.  It was something
> that didn't get cleaned up in a previous hosting move.

Actually one other thing that just occurred to me is that they might be
upset by the mails I send telling people I've applied their patches.  If
that is the case I'm really not sure what to do.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL] regmap updates for v4.15

[Linus Torvalds]

On Mon, Nov 13, 2017 at 9:16 AM, Mark Brown <broonie@kernel.org> wrote:
>
> Are you sure you're seeing stuff from sirena.org.uk and not
> sirena.co.uk?  That's the envelope sender, I changed it after the last
> time this happened to see if that helped.  The hosts it goes through are
> still on .org.uk though.

I'm sure I tried sirena.org.uk - I can check my bash history.

But now that I try again, neither sirena.co.uk nor sirena.org.uk show
it. You have both in your emails, with

  mailed-by: sirena.co.uk
  signed-by: sirena.org.uk

and then a From: kernel.org, so it all looks understandably dodgy to gmail.

And apparently the DNS hijacking thing is only occasional. Although:

> I've deleted that A record, hopefully that'll help.  It was something
> that didn't get cleaned up in a previous hosting move.

Oh, that may be what makes it fail properly now.

> The other thing I'm aware of is that SBL-CSS keeps continually listing
> my outbound mail relay

Oh, that would do it too. But maybe spamhaus hated you exactly because
of that dodgy music site thing.

Anybody who spells "gigs" with a "z" is obviously suspect, so you
can't trust people like that.

              Linus

Re: [GIT PULL] regmap updates for v4.15

[Linus Torvalds]

On Mon, Nov 13, 2017 at 9:26 AM, Mark Brown <broonie@kernel.org> wrote:
>
> Actually one other thing that just occurred to me is that they might be
> upset by the mails I send telling people I've applied their patches.  If
> that is the case I'm really not sure what to do.

If those people then mark you as spam, then gmail would probably notice.

But I don't think you apply sufficient numbers of patches for gmail to
really care. People like David Miller, yes. But even his emails don't
get hated on by gmail.

So I think it's more likely that it's the spamhaus listing.

                   Linus

Re: [GIT PULL] regmap updates for v4.15

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1611 bytes --]

On Mon, Nov 13, 2017 at 09:28:43AM -0800, Linus Torvalds wrote:
> On Mon, Nov 13, 2017 at 9:16 AM, Mark Brown <broonie@kernel.org> wrote:

> > Are you sure you're seeing stuff from sirena.org.uk and not
> > sirena.co.uk?  That's the envelope sender, I changed it after the last
> > time this happened to see if that helped.  The hosts it goes through are
> > still on .org.uk though.

> I'm sure I tried sirena.org.uk - I can check my bash history.

> But now that I try again, neither sirena.co.uk nor sirena.org.uk show
> it. You have both in your emails, with

>   mailed-by: sirena.co.uk
>   signed-by: sirena.org.uk

> and then a From: kernel.org, so it all looks understandably dodgy to gmail.

I don't think it's the signature vs sender thing, it was upset before
that (when everything except the From showed .org.uk), that's why I
changed to use .co.uk.  I've switched back now, perhaps it'll help a
little.

> > The other thing I'm aware of is that SBL-CSS keeps continually listing
> > my outbound mail relay

> Oh, that would do it too. But maybe spamhaus hated you exactly because
> of that dodgy music site thing.

> Anybody who spells "gigs" with a "z" is obviously suspect, so you
> can't trust people like that.

It's possible it was that, but it's really hard to tell without any
reporting from them.  Like I said in my other mail my patch applied
mails (which are auto generated in batches when I push things out) might
be triggering.  I'm going to try washing stuff through Google and see if
that helps but that'll need to wait a while as the relay setup takes a
while to propagate they say.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: [GIT PULL] regmap updates for v4.15

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

On Mon, Nov 13, 2017 at 09:30:28AM -0800, Linus Torvalds wrote:
> On Mon, Nov 13, 2017 at 9:26 AM, Mark Brown <broonie@kernel.org> wrote:

> > Actually one other thing that just occurred to me is that they might be
> > upset by the mails I send telling people I've applied their patches.  If
> > that is the case I'm really not sure what to do.

> If those people then mark you as spam, then gmail would probably notice.

It's a *relatively* big form letter that gets sent out a lot (with the
patch at the bottom) so I can see automated stuff picking up on it as me
trying to sell people hot kernel contributions or whatever.

> But I don't think you apply sufficient numbers of patches for gmail to
> really care. People like David Miller, yes. But even his emails don't
> get hated on by gmail.

> So I think it's more likely that it's the spamhaus listing.

I was more thinking about spamhaus listing based on the applied mails, I
guess Google could do it directly too.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]