[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173316099889.156452.1327566549326122960.b4-ty@kernel.org>
Date: Mon, 02 Dec 2024 17:36:38 +0000
From: Mark Brown <broonie@...nel.org>
To: robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
vaishnav.a@...com, Srikanth Boyapally <srikanth.boyapally@....com>
Cc: linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, git@....com, srinivas.goud@....com,
radhey.shyam.pandey@....com, srikanthboyapally2016@...il.com,
sai.krishna.potthuri@....com
Subject: Re: [PATCH 0/3] spi: cadence-quadspi: Add support for device reset
On Wed, 20 Nov 2024 17:39:48 +0530, Srikanth Boyapally wrote:
> Add support for device reset via OSPI on Versal Gen 2 platform.
>
> Srikanth Boyapally (3):
> dt-bindings: qspi: cdns,qspi-nor: Add compatible string to support
> OSPI controller on Versal Gen2 platform
> spi: cadence-quadspi: Use quirks to set dma_set_mask instead of
> compatible string for 64-bit DMA support
> spi: cadence-quadspi: Support for device reset via OSPI controller
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/3] dt-bindings: qspi: cdns,qspi-nor: Add compatible string to support OSPI controller on Versal Gen2 platform
commit: 707080d4fea8f6b8319ceead569f34c2be5bf1d5
[2/3] spi: cadence-quadspi: Use quirks to set dma_set_mask instead of compatible string for 64-bit DMA support
commit: 2e4d9f5111a3b3c24550e34710efa690c03b3ea1
[3/3] spi: cadence-quadspi: Support for device reset via OSPI controller
commit: 27cf57f65bea55d985f0ad0dc1737ce1d01f05dc
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