linux-kernel - Re: [PATCH] spi: spi-loopback-test: Add module param for iteration length

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: <168140836477.1052939.3678951813615163039.b4-ty@kernel.org>
Date:   Thu, 13 Apr 2023 18:52:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Rohit Ner <rohitner@...gle.com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
        Manu Gautam <manugautam@...gle.com>,
        Joy Chakraborty <joychakr@...gle.com>
Subject: Re: [PATCH] spi: spi-loopback-test: Add module param for iteration
 length

On Mon, 03 Apr 2023 09:39:10 +0530, Rohit Ner wrote:
> SPI test framework is designed to run each test case for
> a list of lengths.
> Introduce a module parameter to limit the iterations
> to a single value among the list of lengths.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-loopback-test: Add module param for iteration length
      commit: 6d87552c0b86b9677d762002082df5f5b7e3c33f

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