Re: [PATCH 0/8] spi: Build coverage cleanups and improvements

[Mark Brown <broonie@xxxxxxxxxx>]

On Thu, 23 Feb 2023 17:20:20 +0000, Mark Brown wrote:
> This series opens up build coverage of a bunch of SPI drivers by
> allowing build under COMPILE_TEST where possible, while also adding
> appropriate architecture specific dependencies to a couple of drivers
> that didn't have them so they don't show up in builds when they're not
> useful.  We also have one fix for the dependencies of the s3c24xx driver
> which was turned up in the process of doing this.
> 
> [...]

Applied to

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

Thanks!

[1/8] spi: s3c24xx: Fix dependencies when FIQ support is enabled
      (no commit info)
[2/8] spi: rockchip: Add architecture dependency
      commit: 330a200d360f8b140b31d7da8b657da0472484e6
[3/8] spi: nxp-flexspi: Fix ARCH_LAYERSCAPE dependency
      commit: c6b15b2437a10b7b381d32f4a5341f655bfa296f
[4/8] spi: davinci: Make available for build test
      commit: e48d57d7203441b7a32b4275462ebb9296ea3fa0
[5/8] spi: fsi: Make available for build test
      commit: f916c7080d28831493518364492e33fc6a437907
[6/8] spi: qcom-qspi: Make available for build test
      commit: ada850541ad33f621425a382d0810b839cb3169e
[7/8] spi: s3c24xx: Only have compile time references to FIQ when building it
      (no commit info)
[8/8] spi: s3c24xx: Allow build test coverage
      (no commit info)

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