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.10
Date: Mon, 13 May 2024 10:38:26 +0100 [thread overview]
Message-ID: <be1cf843f7131a702c3eebab6abaa82d.broonie@kernel.org> (raw)
The following changes since commit 70ee853eec5693fefd8348a2b049d9cb83362e58:
regmap: Add regmap_read_bypassed() (2024-04-08 14:09:58 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.10
for you to fetch changes up to 9b1fe0510494c989ab6a131ce8b97cdd02a1c869:
regmap: Reorder fields in 'struct regmap_config' to save some memory (2024-05-07 10:31:42 +0900)
----------------------------------------------------------------
regmap: Updates for v6.10
Other than a few cleanups the changes here are all in the KUnit tests,
Richard Fitzgerald sent some bug fixes during the v6.9 cycle and while
adding test coverage for the issues fixed did some fairly substantial
improvements, both cleaning up the framework and building out the
coverage.
----------------------------------------------------------------
Andy Shevchenko (2):
regmap: Drop capitalisation in MODULE_DESCRIPTION()
regmap: spi: Add missing MODULE_DESCRIPTION()
Christophe JAILLET (1):
regmap: Reorder fields in 'struct regmap_config' to save some memory
Colin Ian King (1):
regmap: maple: Remove second semicolon
Dan Carpenter (1):
regmap: kunit: Fix an NULL vs IS_ERR() check
Mark Brown (1):
regmap: kunit: Add some test cases and a few small
Richard Fitzgerald (11):
regmap: kunit: Fix warnings of implicit casts to __le16 and __be16
regmap: kunit: Create a struct device for the regmap
regmap: kunit: Introduce struct for test case parameters
regmap: kunit: Run sparse cache tests at non-zero register addresses
regmap: kunit: Run non-sparse cache tests at non-zero register addresses
regmap: kunit: Add more cache-drop tests
regmap: kunit: Add more cache-sync tests
regmap: kunit: Use a KUnit action to call regmap_exit()
regmap: kunit: Replace a kmalloc/kfree() pair with KUnit-managed alloc
regmap: kunit: Add cache-drop test with multiple cache blocks
regmap: kunit: Add test cases for regmap_read_bypassed()
drivers/base/regmap/internal.h | 14 +-
drivers/base/regmap/regcache-maple.c | 2 +-
drivers/base/regmap/regmap-i3c.c | 2 +-
drivers/base/regmap/regmap-kunit.c | 990 ++++++++++++++++++++++++++---------
drivers/base/regmap/regmap-mdio.c | 2 +-
drivers/base/regmap/regmap-ram.c | 5 +-
drivers/base/regmap/regmap-raw-ram.c | 5 +-
drivers/base/regmap/regmap-sdw-mbq.c | 2 +-
drivers/base/regmap/regmap-sdw.c | 2 +-
drivers/base/regmap/regmap-spi.c | 1 +
include/linux/regmap.h | 62 +--
11 files changed, 800 insertions(+), 287 deletions(-)
next reply other threads:[~2024-05-13 9:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 9:38 Mark Brown [this message]
2024-05-14 21:44 ` [GIT PULL] regmap updates for v6.10 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=be1cf843f7131a702c3eebab6abaa82d.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).