spi: hisi-sfc-v3xx: Propagate errors from optional IRQ lookup
Subsystems (2)
PATCH 1/1 spi: hisi-sfc-v3xx: Propagate errors from optional IRQ lookup
From: bui duc phuc <[email protected]>
platform_get_irq_optional() returns a positive IRQ number on success or a negative error code on failure. For an optional IRQ, -ENXIO indicates that no IRQ is available, while other errors should be propagated.
Instead of only checking for -EPROBE_DEFER, propagate all error codes returned by platform_get_irq_optional() other than -ENXIO, so that failures are properly reported to the caller.
--- drivers/spi/spi-hisi-sfc-v3xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/spi/spi-hisi-sfc-v3xx.c +2 -2
@@ -454,8 +454,8 @@ static int hisi_sfc_v3xx_probe(struct platform_device *pdev)return PTR_ERR (host->regbase); host->irq =platform_get_irq_optional (pdev,0 ); -if (host->irq == -EPROBE_DEFER ) -return -EPROBE_DEFER ; +if (host->irq <0 && host->irq != -ENXIO ) +return host->irq;hisi_sfc_v3xx_disable_int (host);
Signature · 1 line
2.43.0
Mark Brown
maintainerQuoted 1 line · On Fri, 07 Aug 2026 17:38:47 +0700, [email protected] wrote:
spi: hisi-sfc-v3xx: Propagate errors from optional IRQ lookup
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.3
Thanks!
[1/1] spi: hisi-sfc-v3xx: Propagate errors from optional IRQ lookup
https://git.kernel.org/broonie/spi/c/e4702b6ff30e
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