From: Mark Brown <broonie@kernel.org>
To: Hector Martin <marcan@marcan.st>,
linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 0/2] regmap: kunit: Add test for cache sync interaction with range selectors
Date: Thu, 26 Oct 2023 19:16:47 +0100 [thread overview]
Message-ID: <169834420703.160082.7535557805517818126.b4-ty@kernel.org> (raw)
In-Reply-To: <20231023-regmap-test-window-cache-v1-0-d8a71f441968@kernel.org>
On Mon, 23 Oct 2023 18:19:10 +0100, Mark Brown wrote:
> 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.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/2] regmap: kunit: Fix marking of the range window as volatile
commit: fabe32cc1eca7857837abcb56b242bc4845b7067
[2/2] regmap: kunit: Add test for cache sync interaction with ranges
commit: 6a2e332c2cbddd17d7dcb8f334953593f1324c8e
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2023-10-26 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 17:19 Mark Brown
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 ` Mark Brown [this message]
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=169834420703.160082.7535557805517818126.b4-ty@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 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®