2023-11-03 18:44:26

by Pandey, Radhey Shyam

[permalink] [raw]
Subject: [PATCH] spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies

From: Amit Kumar Mahapatra <[email protected]>

Zynq QSPI driver has been converted to use spi-mem framework so
add spi-mem to driver kconfig dependencies.

Fixes: 67dca5e580f1 ("spi: spi-mem: Add support for Zynq QSPI controller")
Signed-off-by: Amit Kumar Mahapatra <[email protected]>
Signed-off-by: Radhey Shyam Pandey <[email protected]>
---
drivers/spi/Kconfig | 1 +
1 file changed, 1 insertion(+)

diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index c7b8596cf990..1336815a0c2c 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -1158,6 +1158,7 @@ config SPI_XTENSA_XTFPGA
config SPI_ZYNQ_QSPI
tristate "Xilinx Zynq QSPI controller"
depends on ARCH_ZYNQ || COMPILE_TEST
+ depends on SPI_MEM
help
This enables support for the Zynq Quad SPI controller
in master mode.
--
2.34.1


2023-11-06 13:04:25

by Mark Brown

[permalink] [raw]
Subject: Re: [PATCH] spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies

On Sat, 04 Nov 2023 00:13:51 +0530, Radhey Shyam Pandey wrote:
> Zynq QSPI driver has been converted to use spi-mem framework so
> add spi-mem to driver kconfig dependencies.
>
>

Applied to

https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: spi-zynq-qspi: add spi-mem to driver kconfig dependencies
commit: c2ded280a4b1b7bd93e53670528504be08d24967

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