Re: [PATCH v1 0/5] spi: mpc5xxx-psc: Clean up even more and fix

[Mark Brown]

On Mon, 06 Mar 2023 20:31:10 +0200, Andy Shevchenko wrote:
> The recent cleanup series broke the error path in the drivers.
> So fix it and do even more cleanups.
> 
> Andy Shevchenko (5):
>   spi: mpc5xxx-psc: Correct error check for
>     devm_platform_get_and_ioremap_resource()
>   spi: mpc5xxx-psc: Return immediately if IRQ resource is unavailable
>   spi: mpc5xxx-psc: use devm_clk_get_enabled() for core clock
>   spi: mpc5xxx-psc: Propagate firmware node
>   spi: mpc5xxx-psc: Consistently use device property APIs
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: mpc5xxx-psc: Correct error check for devm_platform_get_and_ioremap_resource()
      commit: ee493fa5d91dec02402239a072820b18beb36265
[2/5] spi: mpc5xxx-psc: Return immediately if IRQ resource is unavailable
      commit: 208ee586f86237969a91ac60ea10f48db9135143
[3/5] spi: mpc5xxx-psc: use devm_clk_get_enabled() for core clock
      commit: 9e21720a49589304aef9e37e8b6c6a4196daf156
[4/5] spi: mpc5xxx-psc: Propagate firmware node
      commit: 289c084ddc1317e6ed911911f95371679c10af1e
[5/5] spi: mpc5xxx-psc: Consistently use device property APIs
      commit: 3169c5816a55ba671e9c8a671c6c75818d30c657

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