linux-kernel - Re: [PATCH next] spi: spi-pci1xxxx: Fix error code in probe

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: <174947644859.127013.15989165632026703633.b4-ty@kernel.org>
Date: Mon, 09 Jun 2025 14:40:48 +0100
From: Mark Brown <broonie@...nel.org>
To: Thangaraj Samynathan <thangaraj.s@...rochip.com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] spi: spi-pci1xxxx: Fix error code in probe

On Fri, 06 Jun 2025 12:04:14 +0300, Dan Carpenter wrote:
> Return the error code if pci_alloc_irq_vectors() fails.  Don't return
> success.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi-pci1xxxx: Fix error code in probe
      commit: 2b74aea6d078ade810a3b0f7d1bcfcba2eaad416

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