linux-kernel - Re: [PATCH 0/2] spi: cadence-quadspi: Fix probe error path and logging

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: <176605036414.87569.10391818297150077809.b4-ty@kernel.org>
Date: Thu, 18 Dec 2025 09:32:44 +0000
From: Mark Brown <broonie@...nel.org>
To: Anurag Dutta <a-dutta@...com>
Cc: grmoore@...nsource.altera.com, nm@...com, francesco@...cini.it, 
 s-vadapalli@...com, linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 gehariprasath@...com, u-kumar1@...com
Subject: Re: [PATCH 0/2] spi: cadence-quadspi: Fix probe error path and
 logging

On Fri, 12 Dec 2025 12:53:10 +0530, Anurag Dutta wrote:
> This series addresses issues in the cadence-quadspi driver's probe
> error path:
> 
> Patch 1 fixes a clock disable imbalance that occurs when probe fails
> after runtime PM is enabled, particularly when DMA request returns
> -EPROBE_DEFER.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: cadence-quadspi: Add error logging for DMA request failure
      commit: b1f54d7143e0f527cca1091857a786e278d72184
[2/2] spi: cadence-quadspi: Fix clock disable on probe failure path
      commit: 1889dd2081975ce1f6275b06cdebaa8d154847a9

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