Re: [PATCH] spi: fsi: Fix contention in the FSI2SPI engine

[Mark Brown <broonie@xxxxxxxxxx>]

On Tue, 26 Oct 2021 14:33:27 -0500, Eddie James wrote:
> There was nothing to protect multiple SPI controllers on the same FSI2SPI
> device from being accessed through the FSI2SPI device at the same time.
> For example, multiple writes to the command and data registers might occur
> for different SPI controllers, resulting in complete chaos in the SPI
> engine. To prevent this, add a FSI2SPI device level mutex and lock it in
> the SPI register read and write functions.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: fsi: Fix contention in the FSI2SPI engine
      commit: e954af1343f6334bf7e081f2631cc2902d07a0ee

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