Message ID | cover.1600931476.git.michal.simek@xilinx.com (mailing list archive) |
---|---|
Headers | show |
Series | spi: spi-zynqmp-gqspi: Update driver to use spi-mem framework | expand |
On Thu, 24 Sep 2020 09:11:16 +0200, Michal Simek wrote: > I am resending this series instead of Amit because his patches are broken > in lore. Mark has reported the issue with it and I clearly see that patch > is broken in lore. > For example: > https://lore.kernel.org/linux-spi/20200922164016.30979-2-amit.kumar-mahapatra@xilinx.com/raw > > There is additional = which shouldn't be there. > @@ -183,7 +184,7 @@ static u32 zynqmp_gqspi_read(struct zynqmp_qspi *xqspi,= > u32 offset) > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/3] spi: spi-zynqmp-gqspi: Fix kernel-doc warnings commit: 91af6eb04a6bbdb8bec8ed6d8ac7850a26604bad [2/3] spi: spi-zynqmp-gqspi: Update driver to use spi-mem framework commit: 1c26372e5aa9e53391a1f8fe0dc7cd93a7e5ba9e [3/3] spi: spi-zynqmp-gqspi: Fix incorrect indentation commit: f09a433b1e4057e6379b7e1207548fff30d5dca3 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