Re: [PATCH 00/11] spi: remove redundant pm_runtime_dont_use_autosuspend() calls

From: Mark Brown

Date: Mon Nov 09 2026 - 17:45:05 EST


On Sun, 08 Nov 2026 13:16:47 +0100, Joshua Crofts wrote:
> spi: remove redundant pm_runtime_dont_use_autosuspend() calls
>
> Since commit d1706f9da9f4 ("PM: runtime: call pm_runtime_dont_use_autosuspend() on reinit()"),
> driver core is now responsible for undoing any
> pm_runtime_use_autosuspend() calls on driver exit.
>
> Remove the redundant function calls.
>
> [...]

Applied to

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

Thanks!

[01/11] spi: axiado: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/9c5ba93a5a13
[02/11] spi: cadence-quadspi: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/4a1cab30f7e0
[03/11] spi: cadence: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/e5187e13ce1f
[04/11] spi: stm32: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/6d2a6ec8942d
[05/11] spi: stm32-qspi: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/73f3bb4134f4
[06/11] spi: zynqmp-gqspi: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/affeee16b705
[07/11] spi: mtk-nor: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/634d73e929cb
[08/11] spi: orion: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/ca8b81eca7f1
[09/11] spi: rockchip-sfc: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/b90c9acd16cb
[10/11] spi: rtk-nor: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/1fcfd0275515
[11/11] spi: tegra210-quad: remove redundant pm_runtime_dont_use_autosuspend() calls
https://git.kernel.org/broonie/spi/c/ff3bd58298fc

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