mbox series

[0/3] regmap: Add KUnit tests for read/write checking

Message ID 20230613-regmap-kunit-read-write-v1-0-2db337c52827@kernel.org
Headers
Series regmap: Add KUnit tests for read/write checking |

Message

Mark Brown June 13, 2023, 8:17 p.m. UTC 
  Since Takashi found an issue with maple tree syncing registers it
shouldn't do add some test cases that catch that case and some more
potential issues, ideally we'd run through the combination of
readability with all possible I/O calls but that's lifting for another
day.  We did find one issue with missing readability checks which will 
be fixed separately.

Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (3):
      regmap: Add test that writes to write only registers are prevented
      regmap: Add a test case for write only registers
      regmap: Add test to make sure we don't sync to read only registers

 drivers/base/regmap/regmap-kunit.c | 115 +++++++++++++++++++++++++++++++++++++
 1 file changed, 115 insertions(+)
---
base-commit: ecfb8ce26d02ec136b4e1ae8c5a77d22d335057b
change-id: 20230613-regmap-kunit-read-write-024393cdbef0

Best regards,

Comments

Mark Brown June 14, 2023, 5:36 p.m. UTC | #1 
On Tue, 13 Jun 2023 21:17:41 +0100, Mark Brown wrote:
> Since Takashi found an issue with maple tree syncing registers it
> shouldn't do add some test cases that catch that case and some more
> potential issues, ideally we'd run through the combination of
> readability with all possible I/O calls but that's lifting for another
> day.  We did find one issue with missing readability checks which will
> be fixed separately.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/3] regmap: Add test that writes to write only registers are prevented
      commit: 180033061e203a7c5510e7c38bccd885657de517
[2/3] regmap: Add a test case for write only registers
      commit: a07bff4054c9e2b3a5c5790312a4a45aaeca7afe
[3/3] regmap: Add test to make sure we don't sync to read only registers
      commit: 357a1ebd0c012f5421252547ebf4ee619b45733d

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