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 updates for v6.7
Date: Mon, 30 Oct 2023 13:33:54 +0000	[thread overview]
Message-ID: <20231030133404.256A7C433C7@smtp.kernel.org> (raw)

The following changes since commit c6df843348d6b71ea986266c12831cb60c2cf325:

  regmap: fix NULL deref on lookup (2023-10-09 13:13:53 +0100)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.7

for you to fetch changes up to 6bbebcc11a69aef269eb2a33212f76992a4cfb1a:

  regmap: Merge up fix for window/paging issue (2023-10-30 13:05:15 +0000)

----------------------------------------------------------------
regmap: Updates for v6.7

The main change here is a fix for an issue where we were letting the
selector for windowed register ranges get out of sync with the hardware
during a cache sync plus associated KUnit tests.  This was reported just
at the end of the release cycle and only in -next for a day prior to the
merge window so it seemed better to hold off for now, the bug had been
present for more than a decade so wasn't causing too many practical
problems hopefully.  There's also a fix for error handling in the
debugfs output from Christope Jaillet.

----------------------------------------------------------------
Christophe JAILLET (1):
      regmap: debugfs: Fix a erroneous check after snprintf()

Mark Brown (4):
      regmap: kunit: Fix marking of the range window as volatile
      regmap: kunit: Add test for cache sync interaction with ranges
      regmap: Ensure range selector registers are updated after cache sync
      regmap: Merge up fix for window/paging issue

 drivers/base/regmap/regcache.c       | 30 ++++++++++++++++
 drivers/base/regmap/regmap-debugfs.c |  2 +-
 drivers/base/regmap/regmap-kunit.c   | 68 ++++++++++++++++++++++++++++++++++--
 3 files changed, 96 insertions(+), 4 deletions(-)

             reply	other threads:[~2023-10-30 13:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30 13:33 Mark Brown [this message]
2023-11-01  3:50 ` [GIT PULL] regmap updates for v6.7 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=20231030133404.256A7C433C7@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