[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <173446006475.142278.5557207366372183006.b4-ty@kernel.org>
Date: Tue, 17 Dec 2024 18:27:44 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Csókás, Bence <csokas.bence@...lan.hu>
Cc: Tudor Ambarus <tudor.ambarus@...aro.org>,
Varshini Rajendran <varshini.rajendran@...rochip.com>,
Nicolas Ferre <nicolas.ferre@...rochip.com>,
Alexandre Belloni <alexandre.belloni@...tlin.com>,
Claudiu Beznea <claudiu.beznea@...on.dev>
Subject: Re: [PATCH v3 0/2] spi: atmel-quadspi: Refactor to allow
supporting SAMA7G5 O/QSPI
On Thu, 28 Nov 2024 18:43:13 +0100, Csókás, Bence wrote:
> This is based on Tudor Ambarus' submission from 2021, and my refactor
> of said sumbission from roughly a month ago.
> Link: https://lore.kernel.org/linux-spi/20211214133404.121739-1-tudor.ambarus@microchip.com/
> Link: https://lore.kernel.org/linux-spi/20241030084445.2438750-1-csokas.bence@prolan.hu/
>
> This time, I submit both my refactor and the diff between it and the
> original submission, rebased on top of Linus' master, namely:
> commit 7d4050728c83 ("Merge tag 'vfs-6.13-rc1.fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs")
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families
commit: c0a0203cf57963792d59b3e4317a1d07b73df42a
[2/2] spi: atmel-quadspi: Add support for sama7g5 QSPI
commit: 5af42209a4d23adc9a09e59e586d1b47fef3cc86
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