Re: [PATCH spi-next 00/11] spi: spi-fsl-lpspi: various cleanup and enhancement patches

[Mark Brown]

On Mon, 16 Mar 2026 09:39:01 +0100, Marc Kleine-Budde wrote:
> While optimizing the spi-fsl-lpspi driver, I created some cleanup and
> enhacement patches.

Applied to

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

Thanks!

[01/11] spi: spi-fsl-lpspi: adapt to kernel coding style
        https://git.kernel.org/broonie/misc/c/8292eded5998
[02/11] spi: spi-fsl-lpspi: fsl_lpspi_probe(): use FIELD_GET to decode Parameter register
        (no commit info)
[03/11] spi: spi-fsl-lpspi: fsl_lpspi_set_cmd(): use FIELD_PREP to encode Transmit Command register
        https://git.kernel.org/broonie/misc/c/c6e178460434
[04/11] spi: spi-fsl-lpspi: fsl_lpspi_set_watermark(): use FIELD_PREP() to encode FIFO Status register
        (no commit info)
[05/11] spi: spi-fsl-lpspi: fsl_lpspi_setup_transfer(): remove useless spi_transfer NULL pointer check
        https://git.kernel.org/broonie/misc/c/ca431d50bf62
[06/11] spi: spi-fsl-lpspi: fsl_lpspi_can_dma(): directly assign return value to fsl_lpspi->usedma
        https://git.kernel.org/broonie/misc/c/e59fe5e0c418
[07/11] spi: spi-fsl-lpspi: fsl_lpspi_reset(): convert to void
        (no commit info)
[08/11] spi: spi-fsl-lpspi: fsl_lpspi_write_tx_fifo(): simplify while() loop check
        https://git.kernel.org/broonie/misc/c/4ef7fa7bca57
[09/11] spi: spi-fsl-lpspi: make struct lpspi_config::mode u32
        https://git.kernel.org/broonie/misc/c/baa1cb259cc7
[10/11] spi: spi-fsl-lpspi: fsl_lpspi_set_cmd(): use mode from (struct fsl_lpspi_data::config::mode
        (no commit info)
[11/11] spi: spi-fsl-lpspi: fsl_lpspi_set_bitrate(): don't treat devtype_data->prescale_max == 0 as a special case
        (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