[PATCH v3 0/9] Some fixes for spi-s3c64xx

[Mark Brown]

On Fri, 2 Oct 2020 14:22:34 +0200, Łukasz Stelmach wrote:
> This is a series of fixes created during porting a device driver (these
> patches will be released soon too) for an SPI device to the current kernel.
> 
> The two most important are
> 
>   spi: spi-s3c64xx: swap s3c64xx_spi_set_cs() and s3c64xx_enable_datapath()
>   spi: spi-s3s64xx: Add S3C64XX_SPI_QUIRK_CS_AUTO for Exynos3250
> 
> [...]

Applied to

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

Thanks!

[1/9] spi: spi-s3c64xx: swap s3c64xx_spi_set_cs() and s3c64xx_enable_datapath()
      commit: 581e2b41977dfc2d4c26c8e976f89c43bb92f9bf
[2/9] spi: spi-s3s64xx: Add S3C64XX_SPI_QUIRK_CS_AUTO for Exynos3250
      commit: ab4efca29f6479bfae6ef433e757014ed6755710
[3/9] spi: spi-s3c64xx: Check return values
      commit: 2f4db6f705c5cba85d23836c19b44d9687dc1334
[4/9] spi: spi-s3c64xx: Report more information when errors occur
      commit: df7cd1bba2c78c04e6a6ed6b95fc3a7b4be83f3a
[5/9] spi: spi-s3c64xx: Rename S3C64XX_SPI_SLAVE_* to S3C64XX_SPI_CS_*
      commit: 913ba5c9e22789ed144a86f002a3e5e8b10c7525
[6/9] spi: spi-s3c64xx: Fix doc comment for struct s3c64xx_spi_driver_data
      commit: 58d54781433f4e02f598e794e1fdb29c3ac07fa1
[7/9] spi: spi-s3c64xx: Ensure cur_speed holds actual clock value
      commit: 20b4016a3bea0ce0a94bf4f20f2a9670ea1dfaa3
[8/9] spi: spi-s3c64xx: Increase transfer timeout
      commit: 9fe26adbe37fddeddb87e45adbc94ce2cd470ff1
[9/9] spi: spi-s3c64xx: Turn on interrupts upon resume
      commit: 3f32131fbbbf86cf44487ce033b2b27380ec49fa

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