All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Hector Martin <marcan@marcan.st>,
	linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors
Date: Mon, 23 Oct 2023 18:19:10 +0100	[thread overview]
Message-ID: <20231023-regmap-test-window-cache-v1-0-d8a71f441968@kernel.org> (raw)

Add a test for a bug reported by Hector Martin, plus a fix for a thinko
in the tests that I spotted while adding that test case.  I've not
included a fix since I believe Hector either has or is working on
something and I don't want to invalidate his work.

Hector also reports that there is a similar interaction around cache
initialisation from device defaults.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (2):
      regmap: kunit: Fix marking of the range window as volatile
      regmap: kunit: Add test for cache sync interaction with ranges

 drivers/base/regmap/regmap-kunit.c | 68 ++++++++++++++++++++++++++++++++++++--
 1 file changed, 65 insertions(+), 3 deletions(-)
---
base-commit: 6465e260f48790807eef06b583b38ca9789b6072
change-id: 20231023-regmap-test-window-cache-c3a2b3d0a769

Best regards,
-- 
Mark Brown <broonie@kernel.org>


             reply	other threads:[~2023-10-23 17:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-23 17:19 Mark Brown [this message]
2023-10-23 17:19 ` [PATCH 1/2] regmap: kunit: Fix marking of the range window as volatile Mark Brown
2023-10-23 17:19 ` [PATCH 2/2] regmap: kunit: Add test for cache sync interaction with ranges Mark Brown
2023-10-26 18:16 ` [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors Mark Brown

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=20231023-regmap-test-window-cache-v1-0-d8a71f441968@kernel.org \
    --to=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcan@marcan.st \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.