Re: [PATCH v2 00/14] spi: pxa2xx: Set of cleanups

[Andy Shevchenko <andy.shevchenko@xxxxxxxxx>]

On Tue, May 11, 2021 at 11:27 AM Mark Brown <broonie@xxxxxxxxxx> wrote:
>
> On Fri, 23 Apr 2021 21:24:27 +0300, Andy Shevchenko wrote:
> > Set of cleanups here and there related to the SPI PXA2xx driver.
> > On top of them, adding the special type for Intel Merrifield.


> [07/14] spi: pxa2xx: Introduce int_stop_and_reset() helper
>         (no commit info)
> [08/14] spi: pxa2xx: Reuse int_error_stop() in pxa2xx_spi_slave_abort()
>         (no commit info)
> [09/14] spi: pxa2xx: Use pxa_ssp_enable()/pxa_ssp_disable() in the driver
>         (no commit info)
> [10/14] spi: pxa2xx: Extract pxa2xx_spi_update() helper
>         (no commit info)
> [11/14] spi: pxa2xx: Extract clear_SSCR1_bits() helper
>         (no commit info)
> [12/14] spi: pxa2xx: Extract read_SSSR_bits() helper
>         (no commit info)
> [13/14] spi: pxa2xx: Constify struct driver_data parameter
>         (no commit info)
> [14/14] spi: pxa2xx: Introduce special type for Merrifield SPIs
>         (no commit info)

The above patches are effectively missed.
Anything to fix in your scripts / my patches?

The below does not shed a light.

> 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.

-- 
With Best Regards,
Andy Shevchenko