This series supersedes the omap2-mcspi patch in the managed controller
allocation series. [1]

Included are also two related cleanups.

Johan


[1] https://lore.kernel.org/lkml/20260429091333.165363-1-johan@kernel.org/


Changes in v2:
 - release DMA resources also if DMA setup fails
 - clean up error labels
 - clean up return value


Johan Hovold (3):
  spi: omap2-mcspi: switch to managed controller allocation
  spi: omap2-mcspi: clean up error labels
  spi: omap2-mcspi: clean up probe return value

 drivers/spi/spi-omap2-mcspi.c | 42 +++++++++++++++--------------------
 1 file changed, 18 insertions(+), 24 deletions(-)

-- 
2.53.0

On Thu, 30 Apr 2026 14:01:57 +0200, Johan Hovold wrote:
> spi: omap2-mcspi: switch to managed controller allocation
> 
> This series supersedes the omap2-mcspi patch in the managed controller
> allocation series. [1]
> 
> Included are also two related cleanups.
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: omap2-mcspi: switch to managed controller allocation
      https://git.kernel.org/broonie/spi/c/caf2fd997bf3
[2/3] spi: omap2-mcspi: clean up error labels
      https://git.kernel.org/broonie/spi/c/186fda6ee1ac
[3/3] spi: omap2-mcspi: clean up probe return value
      https://git.kernel.org/broonie/spi/c/46bd1fafc494

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