Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     andi@etezian.org, krzysztof.kozlowski@linaro.org,
        Vincent Whitchurch <vincent.whitchurch@axis.com>
Cc:     alim.akhtar@samsung.com, linux-samsung-soc@vger.kernel.org,
        linux-spi@vger.kernel.org, kernel@axis.com,
        linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
In-Reply-To: <20220927112117.77599-1-vincent.whitchurch@axis.com>
References: <20220927112117.77599-1-vincent.whitchurch@axis.com>
Subject: Re: [PATCH v2 0/4] spi: Fix DMA bugs in (not only) spi-s3c64xx
Message-Id: <166438602538.235891.3502300542597147263.b4-ty@kernel.org>
Date:   Wed, 28 Sep 2022 18:27:05 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 27 Sep 2022 13:21:13 +0200, Vincent Whitchurch wrote:
> v2:
> - Drop merged patch adding new test to spi-loopback-test
> - Fix compiler warning in !HAS_DMA builds
> - Add support to split transfers to core
> 
> This series fixes some bugs I found while running spi-loopback-test with
> spi-s3c64xx.  The first problem (which I actually noticed while trying to fix
> the second problem with transfers >64KiB) seems to be a generic issue which
> affects several drivers so I fixed it in the core.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/4] spi: Save current RX and TX DMA devices
      commit: f25723dcef4a38f6a39e17afeabd1adf6402230e
[2/4] spi: Fix cache corruption due to DMA/PIO overlap
      commit: 0c17ba73c08ff2690c1eff8df374b6709eed55ce
[3/4] spi: Split transfers larger than max size
      commit: 8d699ff95534747e394e0830399b8d5dcf03e738
[4/4] spi: s3c64xx: Fix large transfers with DMA
      commit: 1224e29572f655facfcd850cf0f0a4784f36a903

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