On Thu, 8 Apr 2021 12:02:19 +0800, quanyang.w...@windriver.com wrote: > This series fix some issues that occurs when the gqspi driver switches to > spi-mem framework. > > Hi Amit, > I rewrite the "Subject" and "commit message" of these patches, so they > look different from the ones which you reviewed before. I still keep > your "Reviewed-by" and hope you will not mind. > > [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: spi-zynqmp-gqspi: use wait_for_completion_timeout to make zynqmp_qspi_exec_op not interruptible commit: a16bff68b75fd082d36aa0b14b540bd7a3ebebbd [2/4] spi: spi-zynqmp-gqspi: add mutex locking for exec_op commit: a0f65be6e880a14d3445b75e7dc03d7d015fc922 [3/4] spi: spi-zynqmp-gqspi: transmit dummy circles by using the controller's internal functionality commit: 8ad07d79bd56a531990a1a3f3f1c0eb19d2de806 [4/4] spi: spi-zynqmp-gqspi: fix incorrect operating mode in zynqmp_qspi_read_op commit: 41d310930084502433fcb3c4baf219e7424b7734 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
