On Mon, 19 Feb 2024 16:33:17 -0600, David Lechner wrote: > This is a follow-up to [1] where it was suggested to break down the > proposed SPI offload support into smaller series. > > This takes on the first suggested task of introducing an API to > "pre-cook" SPI messages. This idea was first discussed extensively in > 2013 [2][3] and revisited more briefly 2022 [4]. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/5] spi: add spi_optimize_message() APIs commit: 7b1d87af14d9ae902ed0c5dc5fabf4eea5abdf02 [2/5] spi: move splitting transfers to spi_optimize_message() commit: fab53fea21a909e4e0656764a8ee7c356fe89d6f [3/5] spi: stm32: move splitting transfers to optimize_message commit: c2bcfe7c6edf418d5adf731a7d60a8abd81e952f [4/5] spi: axi-spi-engine: move message compile to optimize_message commit: 7dba2adb063bcf7a293eacb88980e0975b1fb1fd 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
