From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] Fixes for v5.0
Date: Fri, 18 Jan 2019 12:40:59 +0000 [thread overview]
Message-ID: <20190118124059.GA6260@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1588 bytes --]
The following changes since commit bfeffd155283772bbe78c6a05dec7c0128ee500c:
Linux 5.0-rc1 (2019-01-06 17:08:20 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v5.0-rc2
for you to fetch changes up to 7151449fe7fa5962c6153355f9779d6be99e8e97:
regmap-irq: do not write mask register if mask_base is zero (2019-01-14 22:11:22 +0000)
----------------------------------------------------------------
regmap: Fixes for v5.0
The cleanups for the way we handle type information introduced during
the merge window revealed that we'd been abusing the irq APIs for a long
time, causing breakage for systems. This pull request has a couple of
minimal fixes for that which restore the previous behaviour for the time
being, we'll fix it properly for v5.1 but that'd be a bit much to do as
a bug fix.
----------------------------------------------------------------
There's also this extra merge here which I forgot to get rid of when I
was cleaning up for the major version number change, I only realized
just as I was preparing this and decided it was better to leave it be
rather than rebasing it out and making it look like this stuff hadn't
been sitting in -next.
Mark Brown (1):
Merge branch 'regmap-4.21' into regmap-5.0
Mark Zhang (1):
regmap-irq: do not write mask register if mask_base is zero
Matti Vaittinen (1):
regmap: regmap-irq: silently ignore unsupported type settings
drivers/base/regmap/regmap-irq.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-01-18 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 12:40 Mark Brown [this message]
2019-01-18 19:40 ` [GIT PULL] Fixes for v5.0 pr-tracker-bot
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=20190118124059.GA6260@sirena.org.uk \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).