From: Mark Brown <broonie@kernel.org>
To: linux-spi@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Andi Shyti <andi@etezian.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Eddie James <eajames@linux.ibm.com>, Han Xu <han.xu@nxp.com>,
Haibo Chen <haibo.chen@nxp.com>,
Yogesh Gaur <yogeshgaur.83@gmail.com>,
Heiko Stuebner <heiko@sntech.de>, Mark Brown <broonie@kernel.org>
Subject: [PATCH 0/8] spi: Build coverage cleanups and improvements
Date: Thu, 23 Feb 2023 17:20:20 +0000 [thread overview]
Message-ID: <20230221-spi-arch-deps-v1-0-83d1566474cf@kernel.org> (raw)
This series opens up build coverage of a bunch of SPI drivers by
allowing build under COMPILE_TEST where possible, while also adding
appropriate architecture specific dependencies to a couple of drivers
that didn't have them so they don't show up in builds when they're not
useful. We also have one fix for the dependencies of the s3c24xx driver
which was turned up in the process of doing this.
Signed-off-by: Mark Brown <broonie@kernel.org>
---
Mark Brown (8):
spi: s3c24xx: Fix dependencies when FIQ support is enabled
spi: rockchip: Add architecture dependency
spi: nxp-flexspi: Fix ARCH_LAYERSCAPE dependency
spi: davinci: Make available for build test
spi: fsi: Make available for build test
spi: qcom-qspi: Make available for build test
spi: s3c24xx: Only have compile time references to FIQ when building it
spi: s3c24xx: Allow build test coverage
drivers/spi/Kconfig | 15 +++++++++------
drivers/spi/spi-s3c24xx.c | 4 ++++
2 files changed, 13 insertions(+), 6 deletions(-)
---
base-commit: 7234d746a8339066313518bfa024fa03f363a55e
change-id: 20230221-spi-arch-deps-dba116a915e9
Best regards,
--
Mark Brown <broonie@kernel.org>
next reply other threads:[~2023-02-23 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 17:20 Mark Brown [this message]
2023-02-23 17:20 ` [PATCH 1/8] spi: s3c24xx: Fix dependencies when FIQ support is enabled Mark Brown
2023-02-24 11:05 ` Krzysztof Kozlowski
2023-02-23 17:20 ` [PATCH 2/8] spi: rockchip: Add architecture dependency Mark Brown
2023-02-23 17:20 ` [PATCH 3/8] spi: nxp-flexspi: Fix ARCH_LAYERSCAPE dependency Mark Brown
2023-02-23 17:20 ` [PATCH 4/8] spi: davinci: Make available for build test Mark Brown
2023-02-23 17:20 ` [PATCH 5/8] spi: fsi: " Mark Brown
2023-02-23 17:20 ` [PATCH 6/8] spi: qcom-qspi: " Mark Brown
2023-02-23 17:20 ` [PATCH 7/8] spi: s3c24xx: Only have compile time references to FIQ when building it Mark Brown
2023-02-24 11:06 ` Krzysztof Kozlowski
2023-02-23 17:20 ` [PATCH 8/8] spi: s3c24xx: Allow build test coverage Mark Brown
2023-03-06 13:32 ` [PATCH 0/8] spi: Build coverage cleanups and improvements Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230221-spi-arch-deps-v1-0-83d1566474cf@kernel.org \
--to=broonie@kernel.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=andersson@kernel.org \
--cc=andi@etezian.org \
--cc=eajames@linux.ibm.com \
--cc=haibo.chen@nxp.com \
--cc=han.xu@nxp.com \
--cc=heiko@sntech.de \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-spi@vger.kernel.org \
--cc=yogeshgaur.83@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).