The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 v7.3
Date: Mon, 17 Aug 2026 17:52:39 +0100	[thread overview]
Message-ID: <3bf889c7cf9b7995bcafd594535d6155@kernel.org> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2023 bytes --]

The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:

  Linux 7.2-rc4 (2026-07-19 13:54:41 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v7.3

for you to fetch changes up to ef4f2357df6e9dd6213ce00d01253f3c458d5df0:

  regmap: clean up kernel-doc comments (2026-07-23 19:21:13 +0100)

----------------------------------------------------------------
regmap: Updates for v7.3

This is a relatively busy release, though it's mostly cleanup work.  We
did add some new hooks for regmap-irq to support some driver work, that
should also come in as part of a shared branch with the relevant driver
work in the GPIO subsystem.

----------------------------------------------------------------
Andy Shevchenko (2):
      regcache: Make ->exit() callback return void
      regmap-irq: Provide IRQ resource request and release callbacks

Mark Brown (2):
      regmap-irq: Provide IRQ resource request and release callbacks
      regcache: Warn if regcache_sync() is called in cache_only mode

Randy Dunlap (1):
      regmap: clean up kernel-doc comments

Uwe Kleine-König (The Capable Hub) (1):
      regmap: maple: Workaround for another false-positive compiler warning

bui duc phuc (4):
      regcache: Preserve cache synchronization errors in regcache_sync()
      regcache: Mark cache dirty if selector register rewrite fails
      regcache: Warn if regcache_sync() is called in cache_only mode
      regcache: Validate cache_only state in regcache_sync_region()

 drivers/base/regmap/internal.h        |  2 +-
 drivers/base/regmap/regcache-flat.c   |  4 +---
 drivers/base/regmap/regcache-maple.c  |  8 +++-----
 drivers/base/regmap/regcache-rbtree.c |  8 +++-----
 drivers/base/regmap/regcache.c        | 38 +++++++++++++++++++++++++----------
 drivers/base/regmap/regmap-irq.c      | 22 ++++++++++++++++++++
 include/linux/regmap.h                | 12 +++++++++--
 7 files changed, 67 insertions(+), 27 deletions(-)

                 reply	other threads:[~2026-08-17 16:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3bf889c7cf9b7995bcafd594535d6155@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