linux-kernel - Re: [PATCH v1 for-next] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine

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 for Android: free password hash cracker in your pocket

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

Message-Id: <174983225399.209053.17415046905781410107.b4-ty@kernel.org>
Date: Fri, 13 Jun 2025 17:30:53 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Thangaraj Samynathan <thangaraj.s@...rochip.com>
Cc: UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH v1 for-next] spi: spi-pci1xxxx: Drop MSI-X usage as
 unsupported by DMA engine

On Thu, 12 Jun 2025 08:00:59 +0530, Thangaraj Samynathan wrote:
> Removes MSI-X from the interrupt request path, as the DMA engine used by
> the SPI controller does not support MSI-X interrupts.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-pci1xxxx: Drop MSI-X usage as unsupported by DMA engine
      commit: 9f0ad43b158d07bc7144d219ceabdea36e28e392

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