From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap updates for v5.2
Date: Mon, 6 May 2019 23:17:25 +0900 [thread overview]
Message-ID: <20190506141725.GS14916@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 2373 bytes --]
The following changes since commit 085b7755808aa11f78ab9377257e1dad2e6fa4bb:
Linux 5.1-rc6 (2019-04-21 10:45:57 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v5.2
for you to fetch changes up to 615c4d9a50e25645646c3bafa658aedc22ab7ca9:
Merge branch 'regmap-5.2' into regmap-next (2019-04-25 20:27:04 +0100)
----------------------------------------------------------------
regmap: Updates for v5.2
A larger than usual set of changes, though mainly small:
- An optimization to the debugfs code to greatly improve performance
when dumping extremely sparse register maps from Lucas Tanure.
- Stricter enforcement of writability checks from Han Nandor.
- A fix for default interrupt mode configuration from Srinivas Kandagatla.
- SPDX header conversion from Greg Kroah-Hartman.
----------------------------------------------------------------
Greg Kroah-Hartman (1):
regmap: add proper SPDX identifiers on files that did not have them.
Han Nandor (1):
regmap: verify if register is writeable before writing operations
Lucas Tanure (2):
regmap: debugfs: Replace code by already existing function
regmap: debugfs: Jump to the next readable register
Mark Brown (2):
Merge branch 'regmap-5.1' into regmap-linus
Merge branch 'regmap-5.2' into regmap-next
Srinivas Kandagatla (1):
regmap: regmap-irq: fix getting type default values
drivers/base/regmap/internal.h | 5 +---
drivers/base/regmap/regcache-flat.c | 18 +++++--------
drivers/base/regmap/regcache-lzo.c | 18 +++++--------
drivers/base/regmap/regcache-rbtree.c | 18 +++++--------
drivers/base/regmap/regcache.c | 18 +++++--------
drivers/base/regmap/regmap-ac97.c | 22 ++++------------
drivers/base/regmap/regmap-debugfs.c | 48 ++++++++++++++++++++++-------------
drivers/base/regmap/regmap-i2c.c | 18 +++++--------
drivers/base/regmap/regmap-irq.c | 21 +++++----------
drivers/base/regmap/regmap-mmio.c | 22 ++++------------
drivers/base/regmap/regmap-spi.c | 18 +++++--------
drivers/base/regmap/regmap-spmi.c | 29 ++++++++-------------
drivers/base/regmap/regmap-w1.c | 16 +++++-------
drivers/base/regmap/regmap.c | 27 ++++++++------------
14 files changed, 118 insertions(+), 180 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-05-06 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 14:17 Mark Brown [this message]
2019-05-07 15:10 ` [GIT PULL] regmap updates for v5.2 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=20190506141725.GS14916@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).