Re: [PATCH v7 00/13] spi: spidev_test: new features

[Mark Brown]

On Thu, 24 Sep 2026 15:43:50 +0200, Jonas Rebmann wrote:
> spi: spidev_test: new features
> 
> A collection of new features for spidev_test which have collected during
> testing/development of spi drivers.
> 
> Patch 1 is a small preparatory commit to share macro definitions with
> the rest of the tools tree instead of keeping local copies.
> 
> [...]

Applied to

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

Thanks!

[01/13] spi: spidev_test: include tools/include
        https://git.kernel.org/broonie/spi/c/88ca7a587f73
[02/13] spi: spidev_test: clarify usage for --size
        https://git.kernel.org/broonie/spi/c/a9e74a4c9911
[03/13] spi: spidev_test: make size argument mandatory for --size
        https://git.kernel.org/broonie/spi/c/df79e49bd7d7
[04/13] spi: spidev_test: allow zero-length transfers
        https://git.kernel.org/broonie/spi/c/bd511c42d290
[05/13] spi: spidev_test: abort when -I is selected without -S
        https://git.kernel.org/broonie/spi/c/683d7fac9b0f
[06/13] spi: spidev_test: always compare loopback data
        https://git.kernel.org/broonie/spi/c/2d736e05dbcd
[07/13] spi: spidev_test: add compare mode
        https://git.kernel.org/broonie/spi/c/a47226866b8a
[08/13] spi: spidev_test: allow disabling rx or tx buffers
        https://git.kernel.org/broonie/spi/c/d2b908c75a81
[09/13] spi: spidev_test: don't send 0x0 or 0xff
        https://git.kernel.org/broonie/spi/c/951a60af6c0b
[10/13] spi: spidev_test: send predictable data
        https://git.kernel.org/broonie/spi/c/c807c71d21eb
[11/13] spi: spidev_test: add option to split message into multiple transfers
        https://git.kernel.org/broonie/spi/c/31ce698070aa
[12/13] spi: spidev_test: print TX on error
        https://git.kernel.org/broonie/spi/c/a73c71e1f25a
[13/13] spi: spidev_test: rewrite unescape() to stay in bounds
        https://git.kernel.org/broonie/spi/c/c79bbeadabc0

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