Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
From:   Mark Brown <broonie@kernel.org>
To:     linux-kernel@vger.kernel.org, andreazanottifo@gmail.com,
        linux-spi@vger.kernel.org
In-Reply-To: <20220502111300.24754-1-andreazanottifo@gmail.com>
References: <20220502111300.24754-1-andreazanottifo@gmail.com>
Subject: Re: [PATCH] spi: omap2-mcspi: add support for interword delay
Message-Id: <165169769677.1749597.11425165483130918572.b4-ty@kernel.org>
Date:   Wed, 04 May 2022 21:54:56 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 2 May 2022 13:13:00 +0200, Andrea Zanotti wrote:
> The module omap2-mcspi does not support the interword delay
> parameter present in the spi transfer. On one side, if the module
> is instructed to use the dma, this parameter is correctly ignored.
> However, without the usage of the dma, that parameter should be
> used.
> 
> The patch introduce the handling of such delay in the omap2-mcspi
> module, using standard spi_delay struct. The patch has been tested
> using as benchmark a DM3730.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: omap2-mcspi: add support for interword delay
      commit: 2cd757e6292e23b898791d71978c6edf60a251ad

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