linux-kernel - Re: [PATCH] regmap: kunit: Add a test for ranges in combination with windows

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <170896659074.58811.16405947197376210469.b4-ty@kernel.org>
Date: Mon, 26 Feb 2024 16:56:30 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] regmap: kunit: Add a test for ranges in combination
 with windows

On Sun, 25 Feb 2024 19:49:25 +0000, Mark Brown wrote:
> In preparation for taking advantage of the SPI support for pre-coooked
> messages add a test case covering the use of windows on a raw regmap,
> unfortunately the parameterisation prevents direct reuse and we will
> want to add some raw specific coverage anyway.
> 
> 

Applied to

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

Thanks!

[1/1] regmap: kunit: Add a test for ranges in combination with windows
      commit: bb92804ba2b6636e28db05f589a9a8ef62a07917

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