From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regmap fixes for v5.8-rc5
Date: Fri, 17 Jul 2020 16:42:44 +0100 [thread overview]
Message-ID: <20200717154257.6F8E02076A@mail.kernel.org> (raw)
The following changes since commit 95b2c3ec4cb1689db2389c251d39f64490ba641c:
regmap: Fix memory leak from regmap_register_patch (2020-06-17 17:12:11 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v5.8-rc5
for you to fetch changes up to 299632e54b2e692d2830af84be51172480dc1e26:
regmap: debugfs: Don't sleep while atomic for fast_io regmaps (2020-07-16 20:41:58 +0100)
----------------------------------------------------------------
regmap: Fixes for v5.8
A couple of substantial fixes here, one from Doug which fixes the
debugfs code for MMIO regmaps (fortunately not the common case) and one
from Marc fixing lookups of multiple regmaps for the same device (a very
unusual case). There's also a fix for Kconfig to ensure we enable
SoundWire properly.
----------------------------------------------------------------
Douglas Anderson (1):
regmap: debugfs: Don't sleep while atomic for fast_io regmaps
Marc Kleine-Budde (1):
regmap: dev_get_regmap_match(): fix string comparison
Pierre-Louis Bossart (1):
regmap: add missing dependency on SoundWire
drivers/base/regmap/Kconfig | 2 +-
drivers/base/regmap/regmap-debugfs.c | 52 ++++++++++++++++++++----------------
drivers/base/regmap/regmap.c | 2 +-
3 files changed, 31 insertions(+), 25 deletions(-)
next reply other threads:[~2020-07-17 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-17 15:42 Mark Brown [this message]
2020-07-17 17:40 ` [GIT PULL] regmap fixes for v5.8-rc5 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=20200717154257.6F8E02076A@mail.kernel.org \
--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