linux-kernel - Re: [PATCH v2 for-next] spi: spi-pci1xxxx: Add support for per-instance DMA interrupt vectors

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: <175078642312.219793.13260288534994177625.b4-ty@kernel.org>
Date: Tue, 24 Jun 2025 18:33:43 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Thangaraj Samynathan <thangaraj.s@...rochip.com>
Subject: Re: [PATCH v2 for-next] spi: spi-pci1xxxx: Add support for
 per-instance DMA interrupt vectors

On Tue, 24 Jun 2025 09:00:28 +0530, Thangaraj Samynathan wrote:
> Add support for dedicated DMA interrupt vectors for each SPI hardware
> instance in the pci1xxxx driver. This improves scalability and interrupt
> handling for systems using multiple SPI instances with DMA.
> 
> Introduce a constant `NUM_VEC_PER_INST` to define the number of IRQ
> vectors per instance (main, DMA write, DMA read). Update the
> `pci1xxxx_spi_internal` structure to use an IRQ array.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-pci1xxxx: Add support for per-instance DMA interrupt vectors
      commit: 3e36c822506d924894ff7de549b9377d3114c2d7

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