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 updates for v6.6
Date: Mon, 28 Aug 2023 11:17:18 +0100 [thread overview]
Message-ID: <32ff61b399fada600de5cb9ce363fa9d.broonie@kernel.org> (raw)
The following changes since commit 5d0c230f1de8c7515b6567d9afba1f196fb4e2f4:
Linux 6.5-rc4 (2023-07-30 13:23:47 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.6
for you to fetch changes up to 5d481ddb6a731281238b6a064c719a91f0234b0c:
regmap: Merge up fixes from Linus' tree (2023-07-30 23:35:45 +0100)
----------------------------------------------------------------
regmap: Updates for v6.6
This is a much quieter release than the past few, there's one small API
addition that I noticed a user for in ALSA and a bunch of cleanups:
- Provide an interface for determining if a register is present in the
cache and add a user of it in ALSA.
- Full support for dynamic allocations, following the temporary bodges
that were done as fixes in the previous release.
- Remove the unused and questionably working 64 bit support.
----------------------------------------------------------------
Andy Shevchenko (3):
regmap: Revert "add 64-bit mode support" and Co.
regmap: cache: Revert "Add 64-bit mode support"
regmap: mmio: Remove unused 64-bit support code
Christophe JAILLET (1):
regmap: Fix the type used for a bitmap pointer
Dan Carpenter (1):
regmap: rbtree: Use alloc_flags for memory allocations
Guenter Roeck (2):
regmap: Reject fast_io regmap configurations with RBTREE and MAPLE caches
regmap: maple: Use alloc_flags for memory allocations
Mark Brown (7):
regmap: Provide user selectable option to enable regmap
regmap: Let users check if a register is cached
regmap: Provide test for regcache_reg_present()
ALSA: hda: Use regcache_reg_cached() rather than open coding
regmap: Remove dynamic allocation warnings for rbtree and maple
regmap: Merge up fixes from mainline
regmap: Merge up fixes from Linus' tree
drivers/base/regmap/Kconfig | 12 ++-
drivers/base/regmap/regcache-maple.c | 16 ++--
drivers/base/regmap/regcache-rbtree.c | 12 +--
drivers/base/regmap/regcache.c | 38 +++++----
drivers/base/regmap/regmap-kunit.c | 40 +++++++++
drivers/base/regmap/regmap-mmio.c | 24 ------
drivers/base/regmap/regmap.c | 122 ---------------------------
include/linux/regmap.h | 1 +
sound/hda/hdac_regmap.c | 9 +-
tools/testing/kunit/configs/all_tests.config | 2 +
10 files changed, 94 insertions(+), 182 deletions(-)
next reply other threads:[~2023-08-28 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 10:17 Mark Brown [this message]
2023-08-29 18:08 ` [GIT PULL] regmap updates for v6.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=32ff61b399fada600de5cb9ce363fa9d.broonie@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