From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: [GIT PULL] regmap fixes for v3.17
Date: Thu, 4 Sep 2014 00:08:21 +0100 [thread overview]
Message-ID: <20140903230821.GF29327@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
The following changes since commit 52addcf9d6669fa439387610bc65c92fa0980cef:
Linux 3.17-rc2 (2014-08-25 15:36:20 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v3.17-rc1
for you to fetch changes up to d3b05339873d42a1820d9215ce3885b61d9a95a1:
Merge remote-tracking branches 'regmap/fix/cache', 'regmap/fix/debugfs' and 'regmap/fix/volatile' into regmap-linus (2014-08-31 13:23:45 +0100)
----------------------------------------------------------------
regmap: Fixes for v3.17
Several bug fixes for issues that have been lurking for a while:
- Check that devices haven't set the flag saying they only support
register at a time operation while we're doing cache syncs, otherwise
we fail to restore caches.
- Ensure that we don't mark all registers on devices using format_write()
as cacheable, avoiding adding a cache of things like reset registers
which we don't want to rewrite during cache sync.
- Make sure we create the debugfs files in the correct directory.
----------------------------------------------------------------
Lars-Peter Clausen (1):
regmap: Fix regcache debugfs initialization
Mark Brown (3):
regmap: Fix handling of volatile registers for format_write() chips
regmap: Don't attempt block writes when syncing cache on single_rw devices
Merge remote-tracking branches 'regmap/fix/cache', 'regmap/fix/debugfs' and 'regmap/fix/volatile' into regmap-linus
drivers/base/regmap/internal.h | 3 +++
drivers/base/regmap/regcache-rbtree.c | 9 +++------
drivers/base/regmap/regcache.c | 2 +-
drivers/base/regmap/regmap-debugfs.c | 3 +++
drivers/base/regmap/regmap.c | 2 +-
5 files changed, 11 insertions(+), 8 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2014-09-03 23:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140903230821.GF29327@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
all inboxes | Powered by JetHome®