Re: [PATCH v1 0/6] spi-microchip-core fixes & variable word size support

[Mark Brown <broonie@xxxxxxxxxx>]

On Mon, 15 Jul 2024 12:13:51 +0100, Conor Dooley wrote:
> Hey Mark,
> 
> Got some fixes here for the spi-microchip-core driver, that I am passing
> on.. The author of the first patch is no longer at Microchip, so there's
> probably gonna be some bounces on the series. The remainder of the
> patches got sent in by a user, and, other than one patch, I just wrote
> commit messages for those that were missing them and rebased the series
> on top of mainline.
> 
> [...]

Applied to

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

Thanks!

[1/6] spi: microchip-core: fix the issues in the isr
      commit: 502a582b8dd897d9282db47c0911d5320ef2e6b9
[2/6] spi: microchip-core: defer asserting chip select until just before write to TX FIFO
      commit: 22fd98c107c792e35db7abe45298bc3a29bf4723
[3/6] spi: microchip-core: only disable SPI controller when register value change requires it
      commit: de9850b5c606b754dd7861678d6e2874b96b04f8
[4/6] spi: microchip-core: fix init function not setting the master and motorola modes
      commit: 3a5e76283672efddf47cea39ccfe9f5735cc91d5
[5/6] spi: microchip-core: ensure TX and RX FIFOs are empty at start of a transfer
      commit: 9cf71eb0faef4bff01df4264841b8465382d7927
[6/6] spi: microchip-core: add support for word sizes of 1 to 32 bits
      commit: 87232ea8a5caf8d050f8ea7acd210a2cfcbe6309

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