mirror of https://lore.kernel.org/lkml/
 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 fixes for v7.2-rc7-2
Date: Fri, 14 Aug 2026 18:54:50 +0100	[thread overview]
Message-ID: <a6a7317773d96b32de105f45ec47c4b4@kernel.org> (raw)

The following changes since commit 4b05ccb17f92268384d483221a577fccfc291c7a:

  regcache: Sort the local copy of an unsorted reg_defaults array (2026-08-06 13:01:39 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v7.2-rc7-2

for you to fetch changes up to 00268f9452d2a0d660aa9c1bb0ca07a994af6a4f:

  regmap: sdw-mbq: don't call an unset readable_reg callback (2026-08-12 18:08:48 +0100)

----------------------------------------------------------------
regmap: Final fixes for v7.2

A couple more fixes for regmap, this time for the SoundWire MBQ support.

 - Several drivers omit the readable_reg callback and it's generally
   optional in regmap but the MBQ code had an assumption that one was
   present added in one of the APIs, remove that.
 - The timeout and retry intervals were swapped in read_poll_timeout()
   for soundwire-mbq.

----------------------------------------------------------------
Andrey Golovko (1):
      regmap: sdw-mbq: don't call an unset readable_reg callback

Charles Keepax (1):
      regmap: sdw-mbq: Fix swap of timeout and retry times

 drivers/base/regmap/regmap-sdw-mbq.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

             reply	other threads:[~2026-08-14 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 17:54 Mark Brown [this message]
2026-08-14 22:58 ` 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=a6a7317773d96b32de105f45ec47c4b4@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®