From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, "Csókás,
Bence" <csokas.bence@prolan.hu>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Varshini Rajendran <varshini.rajendran@microchip.com>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Claudiu Beznea <claudiu.beznea@tuxon.dev>
Subject: Re: [PATCH v3 0/2] spi: atmel-quadspi: Refactor to allow supporting SAMA7G5 O/QSPI
Date: Tue, 17 Dec 2024 18:27:44 +0000 [thread overview]
Message-ID: <173446006475.142278.5557207366372183006.b4-ty@kernel.org> (raw)
In-Reply-To: <20241128174316.3209354-1-csokas.bence@prolan.hu>
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
prev parent reply other threads:[~2024-12-17 18:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-28 17:43 [PATCH v3 0/2] spi: atmel-quadspi: Refactor to allow supporting SAMA7G5 O/QSPI Csókás, Bence
2024-11-28 17:43 ` [PATCH v3 1/2] spi: atmel-quadspi: Create `atmel_qspi_ops` to support newer SoC families Csókás, Bence
2024-11-28 17:43 ` [PATCH v3 2/2] spi: atmel-quadspi: Add support for sama7g5 QSPI Csókás, Bence
2024-12-18 9:32 ` Alexander Dahl
2025-01-09 16:27 ` Alexander Dahl
2025-01-09 16:41 ` Mark Brown
2025-01-10 10:40 ` Alexander Dahl
2025-01-14 17:13 ` Csókás Bence
2025-01-10 7:56 ` Alexander Dahl
2025-01-14 17:21 ` Csókás Bence
2024-12-17 18:27 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173446006475.142278.5557207366372183006.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@tuxon.dev \
--cc=csokas.bence@prolan.hu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=tudor.ambarus@linaro.org \
--cc=varshini.rajendran@microchip.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox