[PATCH] spi: qup: Allow for compile-testing on !ARM

[PATCH] spi: qup: Allow for compile-testing on !ARM

[Alex Dewar]

There seems no reason to restrict testing to ARM, so remove this
constraint to improve test coverage.

Build-tested with allyesconfig on x86.

Signed-off-by: Alex Dewar <alex.dewar90@gmail.com>
---
 drivers/spi/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/spi/Kconfig b/drivers/spi/Kconfig
index 01b6c80d86c9..6dd7154d175b 100644
--- a/drivers/spi/Kconfig
+++ b/drivers/spi/Kconfig
@@ -637,7 +637,7 @@ config SPI_QCOM_QSPI
 
 config SPI_QUP
 	tristate "Qualcomm SPI controller with QUP interface"
-	depends on ARCH_QCOM || (ARM && COMPILE_TEST)
+	depends on ARCH_QCOM || COMPILE_TEST
 	help
 	  Qualcomm Universal Peripheral (QUP) core is an AHB slave that
 	  provides a common data path (an output FIFO and an input FIFO)
-- 
2.28.0

Re: [PATCH] spi: qup: Allow for compile-testing on !ARM

[Mark Brown]

On Fri, 4 Sep 2020 17:37:10 +0100, Alex Dewar wrote:
> There seems no reason to restrict testing to ARM, so remove this
> constraint to improve test coverage.
> 
> Build-tested with allyesconfig on x86.

Applied to

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

Thanks!

[1/1] spi: qup: Allow for compile-testing on !ARM
      commit: 2abaad678575acd54e9939e1174becd82ecc884b

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