linux-kernel - Re: [PATCH v10 0/3] Virtio SPI Linux driver

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: <175862672437.1039628.4150229884552248859.b4-ty@kernel.org>
Date: Tue, 23 Sep 2025 13:25:24 +0200
From: Mark Brown <broonie@...nel.org>
To: andriy.shevchenko@...el.com, harald.mommer@....qualcomm.com, 
 quic_msavaliy@...cinc.com, virtio-dev@...ts.linux.dev, 
 viresh.kumar@...aro.org, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, hdanton@...a.com, 
 qiang4.zhang@...ux.intel.com, alex.bennee@...aro.org, 
 Haixu Cui <quic_haixcui@...cinc.com>
Cc: virtualization@...ts.linux-foundation.org, quic_ztu@...cinc.com
Subject: Re: [PATCH v10 0/3] Virtio SPI Linux driver

On Mon, 08 Sep 2025 17:23:45 +0800, Haixu Cui wrote:
> This is the 10th version of the virtio SPI Linux driver patch series which is
> intended to be compliant with the upcoming virtio specification
> version 1.4. The specification can be found in repository:
> https://github.com/oasis-tcs/virtio-spec.git branch virtio-1.4.
> 
> The original contributor Harald submitted:
> RFC v1 to RFC v3
> non-RFC v1 to non-RFC v3
> 
> [...]

Applied to

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

Thanks!

[1/3] virtio: Add ID for virtio SPI
      commit: d9a2211dd3aee3ef29fc675f70a1941bc3f4f51f
[2/3] virtio-spi: Add virtio-spi.h
      commit: 6a1f3390fafeafe130b8128b3047452b92911a98
[3/3] SPI: Add virtio SPI driver
      commit: f98cabe3f6cf6396b3ae0264800d9b53d7612433

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