On Mon, 08 Jul 2024 20:05:27 -0500, David Lechner wrote: > Since the spi-mux controller driver is doing unusual things with SPI > messages, it needs special handling with regard to spi_optimize_message > and friends. > > The main fix along with a detailed explanation is in the second patch. > > The first patch is another unrelated general fix that I noticed while > working on this. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/3] spi: don't unoptimize message in spi_async() commit: c86a918b1bdba78fb155184f8d88dfba1e63335d [2/3] spi: add defer_optimize_message controller flag commit: ca52aa4c60f76566601b42e935b8a78f0fb4f8eb [3/3] spi: mux: set ctlr->bits_per_word_mask commit: c8bd922d924bb4ab6c6c488310157d1a27996f31 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