linux-kernel - Re: [PATCH v1 for-next] spi: spi-pci1xxxx: Fix Probe failure with Dual SPI instance with INTx interrupts

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: <174835173941.43742.10482177523404609545.b4-ty@kernel.org>
Date: Tue, 27 May 2025 14:15:39 +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: Fix Probe failure with
 Dual SPI instance with INTx interrupts

On Tue, 27 May 2025 16:02:44 +0530, Thangaraj Samynathan wrote:
> Fixes a probe failure that occurs when dual SPI controllers are
> enabled and INTx interrupts are used. Reduces the minimum required
> number of interrupt vectors to 1 and registers a shared ISR when
> the allocated vectors are fewer than the number of controllers.
> This change ensures that the probe succeeds even with limited
> vectors, restoring INTx functionality when multiple SPI
> controllers are present.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-pci1xxxx: Fix Probe failure with Dual SPI instance with INTx interrupts
      commit: b4608e944177531334a79f3df2cd14275b47808c

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