[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <170189669029.80266.9452036179086302633.b4-ty@kernel.org>
Date: Wed, 06 Dec 2023 21:04:50 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, David Lechner <dlechner@...libre.com>
Cc: Michael Hennerich <michael.hennerich@...log.com>,
Nuno Sá <nuno.sa@...log.com>,
linux-kernel@...r.kernel.org, Lars-Peter Clausen <lars@...afoo.de>
Subject: Re: [PATCH 0/9] spi: axi-spi-engine: improvements round 2
On Mon, 04 Dec 2023 11:33:26 -0600, David Lechner wrote:
> We are working towards adding support for the offload feature [1] of the
> AXI SPI Engine IP core. Before we can do that, we want to make some
> general fixes and improvements to the driver. In order to avoid a giant
> series with 35+ patches, we are splitting this up into a few smaller
> series.
>
> This is a continuation of the work started in [2] which has been applied
> to spi/for-6.8 [3]. This series must be applied on top of that series to
> apply cleanly.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/9] spi: axi-spi-engine: return void from spi_engine_compile_message()
commit: 2e0d75f8dd9e31b3fb175f780494dd7dd988ceae
[2/9] spi: axi-spi-engine: populate xfer->effective_speed_hz
commit: 9d023ecc31859c7f7c8ca27b5fec52b2dbb8086f
[3/9] spi: axi-spi-engine: remove spi_engine_get_clk_div()
commit: 1fc8dc5721bbc7a21cb4cc60c35eb8031942542b
[4/9] spi: axi-spi-engine: fix sleep ticks calculation
commit: be9070bcf67057b7b03c5acc1980d3897448ad20
[5/9] spi: axi-spi-engine: remove xfer arg from spi_engine_gen_sleep()
commit: e006c181dd9ab006d7b0982d35ef7951fbffe825
[6/9] spi: axi-spi-engine: implement xfer->cs_change_delay
commit: 125a8390995df1a350e9e16e6da11d010e1e7f76
[7/9] spi: axi-spi-engine: restore clkdiv at end of message
commit: 3106edac599f59e1298b034a19a43e7da002fccc
[8/9] spi: axi-spi-engine: remove delay from CS assertion
commit: 0db60d821e485a1c9b8080dbec1ba9871efb6a65
[9/9] spi: axi-spi-engine: add watchdog timer
commit: 07d33c2810bb5fe67747d11f76980ed68602e287
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
Powered by blists - more mailing lists