Messages in this thread | | | From | Mark Brown <> | Subject | Re: [PATCH 00/11] regmap: kunit: Add some test cases and a few small improvements | Date | Wed, 10 Apr 2024 00:34:19 +0100 |
| |
On Mon, 08 Apr 2024 15:45:49 +0100, Richard Fitzgerald wrote: > This series adds some more test cases, mainly for testing: > > commit eaa03486d932 ("regmap: maple: Fix uninitialized symbol 'ret' warnings") > commit 00bb549d7d63 ("regmap: maple: Fix cache corruption in regcache_maple_drop()") > > And the pending patch ("regmap: Add regmap_read_bypassed()") > https://lore.kernel.org/linux-sound/20240408101803.43183-1-rf@opensource.cirrus.com/T/#m2b99b1e01872bfc3597e89dee57dcdd5dbaf1b55 > > [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[01/11] regmap: kunit: Fix warnings of implicit casts to __le16 and __be16 commit: 866f70211bf43927ca44d8e98b5266926fd51315 [02/11] regmap: kunit: Create a struct device for the regmap commit: 7b7982f14315e0f6910e13b22ed38a47144a83ec [03/11] regmap: kunit: Introduce struct for test case parameters commit: 48bccea96fead1b212e19e38e50bf8e69287c45d [04/11] regmap: kunit: Run sparse cache tests at non-zero register addresses commit: 710915743d53d19a1baf0326302aa1f743ab018e [05/11] regmap: kunit: Run non-sparse cache tests at non-zero register addresses commit: ac4394bf9c5e065919a0e491bfd95e2106b1b9b2 [06/11] regmap: kunit: Add more cache-drop tests commit: 7dd52d301cfcff9a67be19d00289e03d80d05e46 [07/11] regmap: kunit: Add more cache-sync tests commit: 7903d15f008056c8c152f2aa3b36217917853264 [08/11] regmap: kunit: Use a KUnit action to call regmap_exit() commit: ce75e06eea9cfdddaa0082cef663cf2d4aa5ed1d [09/11] regmap: kunit: Replace a kmalloc/kfree() pair with KUnit-managed alloc commit: d6f2fd7adcb5f25ac661808be9409f846b1de6fe [10/11] regmap: kunit: Add cache-drop test with multiple cache blocks commit: 468d277e6fb112e7a5e816ef5f1f6bd86c29bea6 [11/11] regmap: kunit: Add test cases for regmap_read_bypassed() commit: f63eb9ae085dc6da27eebfe35317e07a6a02a160
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
| |