[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174562200441.302167.12352642386794751784.b4-ty@kernel.org>
Date: Sat, 26 Apr 2025 00:00:04 +0100
From: Mark Brown <broonie@...nel.org>
To: thierry.reding@...il.com, jonathanh@...dia.com, skomatineni@...dia.com,
ldewangan@...dia.com, linux-spi@...r.kernel.org,
linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
kyarlagadda@...dia.com, smangipudi@...dia.com, Vishwaroop A <va@...dia.com>
Subject: Re: (subset) [PATCH v3 0/6] Configure Clocks, Add Internal DMA
support
On Wed, 16 Apr 2025 11:06:00 +0000, Vishwaroop A wrote:
> This series introduces QSPI clock configuration and internal DMA
> support for Quad SPI controller. The patches have been reorganized
> for better logical flow and review comments from v2 have been addressed.
>
> Vishwaroop A (6):
> spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers
> spi: tegra210-quad: remove redundant error handling code
> spi: tegra210-quad: modify chip select (CS) deactivation
> arm64: tegra: Configure QSPI clocks and add DMA
> spi: tegra210-quad: Update dummy sequence configuration
> spi: tegra210-quad: Add support for internal DMA
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/6] spi: tegra210-quad: Fix X1_X2_X4 encoding and support x4 transfers
commit: dcb06c638a1174008a985849fa30fc0da7d08904
[2/6] spi: tegra210-quad: remove redundant error handling code
commit: 400d9f1a27cc2fceabdb1ed93eaf0b89b6d32ba5
[3/6] spi: tegra210-quad: modify chip select (CS) deactivation
commit: d8966b65413390d1b5b706886987caac05fbe024
[5/6] spi: tegra210-quad: Update dummy sequence configuration
commit: c283fcdc4e2b89678c171691fd26f576139fc256
[6/6] spi: tegra210-quad: Add support for internal DMA
(no commit info)
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