Message ID | 20231018213328.40131-1-amit.kumar-mahapatra@amd.com |
---|---|
Headers | show |
Series | spi: Add support for stacked/parallel memories | expand |
On Thu, Oct 19, 2023 at 03:03:20AM +0530, Amit Kumar Mahapatra wrote: > This patch is in the continuation to the discussions which happened on > 'commit f89504300e94 ("spi: Stacked/parallel memories bindings")' for > adding dt-binding support for stacked/parallel memories. This missed the last release since I'd been hoping for some testing by others with relevant hardware - from a code point of view the SPI bits look fine. Could you resend based on v6.7-rc1 please, it doesn't apply any more?
On Thu, 19 Oct 2023 03:03:20 +0530, Amit Kumar Mahapatra wrote: > This patch is in the continuation to the discussions which happened on > 'commit f89504300e94 ("spi: Stacked/parallel memories bindings")' for > adding dt-binding support for stacked/parallel memories. > > This patch series updated the spi-nor, spi core and the AMD-Xilinx GQSPI > driver to add stacked and parallel memories support. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/8] spi: Add multi-cs memories support in SPI core commit: 4d8ff6b0991d5e86b17b235fc46ec62e9195cb9b [6/8] spi: spi-zynqmp-gqspi: Add stacked memories support in GQSPI driver (no commit info) [8/8] spi: spi-zynqmp-gqspi: Add parallel memories support in GQSPI driver (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