From: Sasha Levin <sashal@kernel.org>
To: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Cc: Wolfram Sang <wsa@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Sasha Levin <sashal@kernel.org>,
krzysztof.kozlowski@canonical.com, yangyicong@hisilicon.com,
semen.protsenko@linaro.org, robh@kernel.org, sven@svenpeter.dev,
jie.deng@intel.com, bence98@sch.bme.hu, lukas.bulwahn@gmail.com,
linux-i2c@vger.kernel.org
Subject: [PATCH AUTOSEL 5.4 11/13] i2c: cadence: allow COMPILE_TEST
Date: Tue, 22 Feb 2022 21:31:15 -0500 [thread overview]
Message-ID: <20220223023118.241815-11-sashal@kernel.org> (raw)
In-Reply-To: <20220223023118.241815-1-sashal@kernel.org>
From: Wolfram Sang <wsa@kernel.org>
[ Upstream commit 0b0dcb3882c8f08bdeafa03adb4487e104d26050 ]
Driver builds fine with COMPILE_TEST. Enable it for wider test coverage
and easier maintenance.
Signed-off-by: Wolfram Sang <wsa@kernel.org>
Acked-by: Michal Simek <michal.simek@xilinx.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
---
drivers/i2c/busses/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 2d08a8719506c..94c78329f841c 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -483,7 +483,7 @@ config I2C_BRCMSTB
config I2C_CADENCE
tristate "Cadence I2C Controller"
- depends on ARCH_ZYNQ || ARM64 || XTENSA
+ depends on ARCH_ZYNQ || ARM64 || XTENSA || COMPILE_TEST
help
Say yes here to select Cadence I2C Host Controller. This controller is
e.g. used by Xilinx Zynq.
--
2.34.1
next prev parent reply other threads:[~2022-02-23 2:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 2:31 [PATCH AUTOSEL 5.4 01/13] mac80211_hwsim: report NOACK frames in tx_status Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 02/13] mac80211_hwsim: initialize ieee80211_tx_info at hw_scan_work Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 03/13] i2c: bcm2835: Avoid clock stretching timeouts Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 04/13] ASoC: rt5668: do not block workqueue if card is unbound Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 05/13] ASoC: rt5682: " Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 06/13] Input: clear BTN_RIGHT/MIDDLE on buttonpads Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 07/13] cifs: fix double free race when mount fails in cifs_get_root() Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 08/13] USB: zaurus: support another broken Zaurus Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 09/13] selftests/ftrace: Do not trace do_softirq because of PREEMPT_RT Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 10/13] dmaengine: shdma: Fix runtime PM imbalance on error Sasha Levin
2022-02-23 2:31 ` Sasha Levin [this message]
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 12/13] i2c: qup: allow COMPILE_TEST Sasha Levin
2022-02-23 2:31 ` [PATCH AUTOSEL 5.4 13/13] net: usb: cdc_mbim: avoid altsetting toggling for Telit FN990 Sasha Levin
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=20220223023118.241815-11-sashal@kernel.org \
--to=sashal@kernel.org \
--cc=bence98@sch.bme.hu \
--cc=jie.deng@intel.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@gmail.com \
--cc=michal.simek@xilinx.com \
--cc=robh@kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=stable@vger.kernel.org \
--cc=sven@svenpeter.dev \
--cc=wsa@kernel.org \
--cc=yangyicong@hisilicon.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