On Mon, 11 May 2026 17:03:56 +0200, Johan Hovold wrote:
> spi: switch to managed controller allocation (part 3/3)
>
> In preparation for fixing the SPI controller API so that it no longer
> drops a reference when deregistering (non-managed) controllers (cf.
> [1]), this series converts drivers using managed registration to also
> use managed allocation.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-7.2
Thanks!
[01/12] spi: altera-platform: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/a7a24f0eaa71
[02/12] spi: armada-3700: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/5b4a0450fe2f
[03/12] spi: clps711x: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/ee9575d2b3db
[04/12] spi: falcon: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/864c368199cf
[05/12] spi: fsi: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/c087eb4603d9
[06/12] spi: hisi-sfc-v3xx: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/572a9fb1a609
[07/12] spi: jcore: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/0a290bb1ff0b
[08/12] spi: lp8841-rtc: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/06ba67d9d479
[09/12] spi: lp8841-rtc: drop unused ifdef
https://git.kernel.org/broonie/spi/c/4fee1d3a563d
[10/12] spi: meson-spifc: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/1e447a5aa124
[11/12] spi: mux: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/60db555fca74
[12/12] spi: xlp: switch to managed controller allocation
https://git.kernel.org/broonie/spi/c/f3d1dc0bc65a
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