Message ID | 20201027095724.18654-1-o.rempel@pengutronix.de (mailing list archive) |
---|---|
Headers | show |
Series | SPI/ Input: ads7846: properly handle spi->mode flags | expand |
On Tue, 27 Oct 2020 10:57:22 +0100, Oleksij Rempel wrote: > changes v2: > - add SPI_MODE_X_MASK macro > - ads7846: clear SPI_MODE_X_MASK bits to set driver specific mode. > > Oleksij Rempel (2): > spi: introduce SPI_MODE_X_MASK macro > Input: ads7846: do not overwrite spi->mode flags set by spi framework > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: introduce SPI_MODE_X_MASK macro commit: 029b42d8519cef70c4fb5fcaccd08f1053ed2bf0 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
On Tue, 27 Oct 2020 10:57:22 +0100, Oleksij Rempel wrote: > changes v2: > - add SPI_MODE_X_MASK macro > - ads7846: clear SPI_MODE_X_MASK bits to set driver specific mode. > > Oleksij Rempel (2): > spi: introduce SPI_MODE_X_MASK macro > Input: ads7846: do not overwrite spi->mode flags set by spi framework > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] Input: ads7846: do not overwrite spi->mode flags set by spi framework commit: 376ccca853fdb9959f7ac5185a428a9f91e71e86 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