Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 28 Jul 2020 17:31:33 +0100
From:   Mark Brown <broonie@kernel.org>
To:     Christian Eggers <ceggers@arri.de>
Cc:     linux-kernel@vger.kernel.org, stable@vger.kernel.org,
        linux-spi@vger.kernel.org
In-Reply-To: <20200728100832.24788-1-ceggers@arri.de>
References: <20200728100832.24788-1-ceggers@arri.de>
Subject: Re: [PATCH] spi: spidev: Align buffers for DMA
Message-Id: <159595388006.15302.11430995371603179380.b4-ty@kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 28 Jul 2020 12:08:32 +0200, Christian Eggers wrote:
> Simply copying all xfers from userspace into one bounce buffer causes
> alignment problems if the SPI controller uses DMA.
> 
> Ensure that all transfer data blocks within the rx and tx bounce buffers
> are aligned for DMA (according to ARCH_KMALLOC_MINALIGN).
> 
> Alignment may increase the usage of the bounce buffers. In some cases,
> the buffers may need to be increased using the "bufsiz" module
> parameter.

Applied to

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

Thanks!

[1/1] spi: spidev: Align buffers for DMA
      commit: aa9e862d7d5bcecd4dca9f39e8b684b93dd84ee7

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