Re: [PATCH 0/5] AMD SPI controller driver bug fix and cleanups

[Mark Brown <broonie@xxxxxxxxxx>]

On Wed, 6 Jul 2022 13:06:21 +0300, Cristian Ciocaltea wrote:
> This patch series addresses an issue in the spi-amd driver and, while
> there, performs some additional cleanups, like simplifying the error
> handling in the probe function and removing an unused struct member.
> 
> For improving code readability, it also adds some kernel-doc comments.
> 
> Cristian Ciocaltea (5):
>   spi: amd: Limit max transfer and message size
>   spi: amd: Make use of devm_spi_alloc_master()
>   spi: amd: Make use of dev_err_probe()
>   spi: amd: Drop io_base_addr member from struct amd_spi
>   spi: amd: Add struct and enum kernel-doc comments
> 
> [...]

Applied to

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

Thanks!

[1/5] spi: amd: Limit max transfer and message size
      commit: 6ece49c56965544262523dae4a071ace3db63507
[2/5] spi: amd: Make use of devm_spi_alloc_master()
      commit: 2e063bb1d4272e7b64ef813566691ea8ea192f9c
[3/5] spi: amd: Make use of dev_err_probe()
      commit: deef4da8be2f7e94a0807e56f856d3e20addce4d
[4/5] spi: amd: Drop io_base_addr member from struct amd_spi
      commit: 1e71ffee97ac02b83b6ff75b52fa7b21b9149f7d
[5/5] spi: amd: Add struct and enum kernel-doc comments
      commit: 55861e36b663f6e584d1b0659c1c5cec0ce26a5d

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