Message ID | 20200526093604.11846-1-vigneshr@ti.com (mailing list archive) |
---|---|
Headers | show |
Series | mtd: spi-nor: Move cadence-qaudspi to spi-mem framework | expand |
On Tue, 26 May 2020 15:05:58 +0530, Vignesh Raghavendra wrote: > This series is a subset of "[PATCH v12 0/4] spi: cadence-quadspi: Add > support for the Cadence QSPI controller" by Ramuthevar,Vadivel MuruganX > <vadivel.muruganx.ramuthevar@linux.intel.com> that intended to move > cadence-quadspi driver to spi-mem framework > > Those patches were trying to accomplish too many things in a single set > of patches and need to split into smaller patches. This is reduced > version of above series. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/6] mtd: spi-nor: cadence-quadspi: Make driver independent of flash geometry commit: 834b4e8d344139ba64cda22099b2b2ef6c9a542d [2/6] mtd: spi-nor: cadence-quadspi: Provide a way to disable DAC mode commit: a99705079a91e6373122bd0ca2fc129b688fc5b3 [3/6] mtd: spi-nor: cadence-quadspi: Don't initialize rx_dma_complete on failure commit: 48aae57f0f9f57797772bd462b4d64902b1b4ae1 [4/6] mtd: spi-nor: cadence-quadspi: Fix error path on failure to acquire reset lines commit: c61088d1f9932940af780b674f028140eda09a94 [5/6] mtd: spi-nor: Convert cadence-quadspi to use spi-mem framework commit: a314f6367787ee1d767df9a2120f17e4511144d0 [6/6] spi: Move cadence-quadspi driver to drivers/spi/ commit: 31fb632b5d43ca16713095b3a4fe17e3d7331e28 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