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.11
Date: Mon, 15 Jul 2024 15:14:40 +0100 [thread overview]
Message-ID: <bc8cbd2e0620ffd78a3a4f71b06a3a88.broonie@kernel.org> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2845 bytes --]
The following changes since commit f2661062f16b2de5d7b6a5c42a9a5c96326b8454:
Linux 6.10-rc5 (2024-06-23 17:08:54 -0400)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.11
for you to fetch changes up to c2bb8198fee88a428513f8d023c627ecd13aa694:
regmap: kunit: Add test cases for regmap_multi_reg_(read,write}() (2024-07-11 12:45:55 +0100)
----------------------------------------------------------------
regmap: Updates for v6.11
There's one new feature here, a regmap_multi_reg_read() matching the
existing write function which has some IIO users coming. This allows
atomic reads from multiple registers without the need to wrap a higher
level lock in the client driver just for regmap (which already has locks
anyway). We also have one fix for the KUnit tests, and a bunch of
cleanups.
----------------------------------------------------------------
Andy Shevchenko (5):
regmap: Switch to use kmemdup_array()
regmap: cache: Use correct type of the rb_for_each() parameter
regmap: cache: Switch to use kmemdup_array()
regmap: maple: Switch to use kmemdup_array()
regmap: kunit: Use array_size() and sizeof(*ptr) consistently
Guenter Roeck (2):
regmap: Implement regmap_multi_reg_read()
regmap: kunit: Add test cases for regmap_multi_reg_(read,write}()
Jeff Johnson (3):
regmap: kunit: add missing MODULE_DESCRIPTION()
regmap-i2c: add missing MODULE_DESCRIPTION() macro
regmap: add missing MODULE_DESCRIPTION() macros
Mark Brown (4):
regmap: Merge up fixes
regmap: Switch to use kmemdup_array()
regmap: Merge up v6.10-rc4
regmap: Implement regmap_multi_reg_read()
Richard Fitzgerald (1):
regmap: kunit: Fix memory leaks in gen_regmap() and gen_raw_regmap()
Thomas Weißschuh (2):
const_structs.checkpatch: add regmap structs
regmap-irq: handle const struct regmap_irq_sub_irq_map
drivers/base/regmap/regcache-maple.c | 13 ++-
drivers/base/regmap/regcache.c | 6 +-
drivers/base/regmap/regmap-ac97.c | 1 +
drivers/base/regmap/regmap-i2c.c | 1 +
drivers/base/regmap/regmap-irq.c | 2 +-
drivers/base/regmap/regmap-kunit.c | 158 +++++++++++++++++++++++++++-------
drivers/base/regmap/regmap-ram.c | 1 +
drivers/base/regmap/regmap-raw-ram.c | 1 +
drivers/base/regmap/regmap-sccb.c | 1 +
drivers/base/regmap/regmap-slimbus.c | 1 +
drivers/base/regmap/regmap-spi-avmm.c | 1 +
drivers/base/regmap/regmap-spmi.c | 1 +
drivers/base/regmap/regmap-w1.c | 1 +
drivers/base/regmap/regmap.c | 105 ++++++++++++++--------
include/linux/regmap.h | 4 +-
scripts/const_structs.checkpatch | 10 +++
16 files changed, 226 insertions(+), 81 deletions(-)
next reply other threads:[~2024-07-15 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:14 Mark Brown [this message]
2024-07-16 1:17 ` 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=bc8cbd2e0620ffd78a3a4f71b06a3a88.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
all inboxes | Powered by JetHome®