Message ID | 20201204193540.3047030-1-swboyd@chromium.org (mailing list archive) |
---|---|
Headers | show |
Series | spi: spi-geni-qcom: Use gpio descriptors for CS | expand |
On Fri, 4 Dec 2020 11:35:37 -0800, Stephen Boyd wrote: > Collected patches from the two series below and associated tags so they > can be merged in one pile through the spi tree. Merry December! > > SPI: https://lore.kernel.org/r/20201202214935.1114381-1-swboyd@chromium.org > cros-ec: https://lore.kernel.org/r/20201203011649.1405292-1-swboyd@chromium.org > > Cc: Akash Asthana <akashast@codeaurora.org> > Cc: Simon Glass <sjg@chromium.org> > Cc: Gwendal Grignou <gwendal@chromium.org> > Cc: Douglas Anderson <dianders@chromium.org> > Cc: Alexandru M Stan <amstan@chromium.org> > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/3] platform/chrome: cros_ec_spi: Don't overwrite spi::mode commit: 74639cbf51d7c0304342544a83dfda354a6bd208 [2/3] platform/chrome: cros_ec_spi: Drop bits_per_word assignment commit: 7a5172b7990d97ab9ef64e6d9063aa68099ea023 [3/3] spi: spi-geni-qcom: Use the new method of gpio CS control commit: 3b25f337929e73232f0aa990cd68a129f53652e2 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