linux-kernel - Re: [PATCH] spi: spi-loopback-test: Allow skipping delays

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: <167276527955.184056.18435028327533008188.b4-ty@kernel.org>
Date:   Tue, 03 Jan 2023 17:01:19 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     kernel@...s.com, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-loopback-test: Allow skipping delays

On Tue, 03 Jan 2023 16:22:10 +0100, Vincent Whitchurch wrote:
> A 100 ms delay is inserted between tests by default in order to "detect
> the individual tests when using a logic analyzer".  However, such delays
> are unnecessary when using this module for automated regression testing,
> so allow them to be disabled with a module parameter.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-loopback-test: Allow skipping delays
      commit: 392af84bddcc96f1546a1ca4ffa71bccce95b897

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