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.6
Date: Mon, 27 Jan 2020 16:55:02 +0000 [thread overview]
Message-ID: <20200127165502.GB3763@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1453 bytes --]
The following changes since commit def9d2780727cec3313ed3522d0123158d87224d:
Linux 5.5-rc7 (2020-01-19 16:02:49 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v5.6
for you to fetch changes up to ea87683909bcda665527a828505c5e9c6a625429:
Merge branch 'regmap-5.6' into regmap-next (2020-01-21 17:29:48 +0000)
----------------------------------------------------------------
regmap: Updates for v5.6
This is quite a busy release for a subsystem that's usually very quiet,
though still a small set of updates in the grand scheme of things:
- A fix for writes to non-incrementing registers.
- An iopoll() style helper for use with atomic safe regmaps, making
it easier to transition from raw memory mapped I/O.
- Some constification.
----------------------------------------------------------------
Ben Whitten (1):
regmap: fix writes to non incrementing registers
Mark Brown (1):
Merge branch 'regmap-5.6' into regmap-next
Michał Mirosław (1):
regmap-i2c: constify regmap_bus structures
Sameer Pujar (1):
regmap: add iopoll-like atomic polling macro
drivers/base/regmap/regmap-i2c.c | 10 ++++-----
drivers/base/regmap/regmap.c | 17 ++++++++++-----
include/linux/regmap.h | 45 ++++++++++++++++++++++++++++++++++++++++
3 files changed, 62 insertions(+), 10 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-01-27 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-27 16:55 Mark Brown [this message]
2020-01-27 19:25 ` [GIT PULL] regmap updates for v5.6 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=20200127165502.GB3763@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).