Message ID | 1612551572-495-1-git-send-email-alain.volmat@foss.st.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: stm32: fix and enhancements for spi-stm32 | expand |
On Fri, 5 Feb 2021 19:59:24 +0100, Alain Volmat wrote: > The serie provides a fix for the spi-stm32 driver, allowing to properly > handle 0 byte transfer (and thus being able to run spi-loopback-test). > > In addition to that, important enhancements are implemented, among them, > supporting transfer larger that what the IP can setup in one go or > allowing to use the SPI bus without cs_gpio. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/8] spi: stm32: properly handle 0 byte transfer commit: 2269f5a8b1a7b38651d62676b98182828f29d11a [2/8] spi: stm32: do not mandate cs_gpio commit: 8f8d0e3e33e36ba63416cad64b9a9ad6b0129eed [3/8] spi: stm32: use bitfield macros commit: 5a380b833ad437123dca91bf900a696709d9b6ab [4/8] spi: stm32h7: ensure message are smaller than max size commit: 084de5232820c9e857ccc2282c3d94f33f92a381 [5/8] spi: stm32: driver uses reset controller only at init commit: 1c75cfd53e213044523141b464eb06813e39ecea [6/8] spi: stm32: defer probe for reset commit: c63b95b76e69b679b9b95014552db099eb77a4fa [7/8] spi: stm32h7: replace private SPI_1HZ_NS with NSEC_PER_SEC commit: e1e2093b16cb1cefe4dc483b00e73d1333260784 [8/8] spi: stm32: make spurious and overrun interrupts visible commit: c64e7efe46b7de21937ef4b3594d9b1fc74f07df 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