public inbox for linux-kernel@vger.kernel.org
 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 v6.4-rc6
Date: Thu, 15 Jun 2023 12:43:07 +0100	[thread overview]
Message-ID: <20230615114317.4B9DAC433C0@smtp.kernel.org> (raw)

The following changes since commit 0cc6578048e0980d254aee345130cced4912f723:

  regmap: maple: Drop the RCU read lock while syncing registers (2023-05-24 11:21:52 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v6.4-rc6

for you to fetch changes up to 44e46572f0bae431a6092e3cfd2f47bff8b8d18c:

  regmap: regcache: Don't sync read-only registers (2023-06-13 13:15:00 +0100)

----------------------------------------------------------------
regmap: One more fix for v6.4

Another fix for the maple tree cache, Takashi noticed that unlike other
caches the maple tree cache didn't check for read only registers before
trying to sync which would result in spurious syncs for read only
registers where we don't have a default.  This was due to the check
being open coded in the caches, we now check in the shared "does this
register need sync" function so that is fixed for this and future
caches.

----------------------------------------------------------------
Takashi Iwai (1):
      regmap: regcache: Don't sync read-only registers

 drivers/base/regmap/regcache.c | 3 +++
 1 file changed, 3 insertions(+)

             reply	other threads:[~2023-06-15 11:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-15 11:43 Mark Brown [this message]
2023-06-16  3:10 ` [GIT PULL] regmap fixes for v6.4-rc6 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=20230615114317.4B9DAC433C0@smtp.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