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 v4.0
Date: Mon, 23 Mar 2015 12:04:15 -0700 [thread overview]
Message-ID: <20150323190414.GQ14954@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:
Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v4.0-rc5
for you to fetch changes up to c6b570d97c0e77f570bb6b2ed30d372b2b1e9aae:
regmap: introduce regmap_name to fix syscon regmap trace events (2015-03-19 20:04:55 +0000)
----------------------------------------------------------------
regmap: Fix for v4.0
This patch fixes a bad interaction between the support that was added
for having regmaps without devices for early system controller
initialization and the trace support. There's a very good analysis of
the actual issue in the commit message for the change.
----------------------------------------------------------------
Philipp Zabel (1):
regmap: introduce regmap_name to fix syscon regmap trace events
drivers/base/regmap/internal.h | 8 +++
drivers/base/regmap/regcache.c | 16 +++---
drivers/base/regmap/regmap.c | 32 +++++------
include/trace/events/regmap.h | 123 ++++++++++++++++++++---------------------
4 files changed, 91 insertions(+), 88 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next reply other threads:[~2015-03-23 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 19:04 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-03-17 11:39 Mark Brown
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=20150323190414.GQ14954@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®