From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: tglx@linutronix.de
Cc: john.stultz@linaro.org, linux-kernel@vger.kernel.org
Subject: [PATCH 7/7] clocksource/drivers/tango: Add COMPILE_TEST option
Date: Thu, 29 Oct 2015 23:52:43 +0100 [thread overview]
Message-ID: <1446159166-20384-7-git-send-email-daniel.lezcano@linaro.org> (raw)
In-Reply-To: <1446159166-20384-1-git-send-email-daniel.lezcano@linaro.org>
Increase the compilation test coverage by adding the COMPILE_TEST option.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
---
drivers/clocksource/Kconfig | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index b92f39d5..4ed76e1 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -285,8 +285,11 @@ config CLKSRC_MIPS_GIC
select CLKSRC_OF
config CLKSRC_TANGO_XTAL
- bool
+ bool "Clocksource for Tango SoC" if COMPILE_TEST
+ depends on ARM
select CLKSRC_OF
+ help
+ This enables the clocksource for Tango SoC
config CLKSRC_PXA
bool "Clocksource for PXA or SA-11x0 platform" if COMPILE_TEST
--
1.9.1
prev parent reply other threads:[~2015-10-29 22:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 22:52 [PATCH 1/7] time: Define dummy functions for the generic sched clock Daniel Lezcano
2015-10-29 22:52 ` [PATCH 2/7] clocksource/drivers/qcom: Make COMPILE_TEST enabled for ARM architecture Daniel Lezcano
2015-10-29 22:52 ` [PATCH 3/7] clocksource/drivers/st_lpc: Fix Kconfig dependency Daniel Lezcano
2015-10-30 8:51 ` Maxime Coquelin
2015-10-29 22:52 ` [PATCH 4/7] clocksource/drivers/st_lpc: Add the COMPILE_TEST option Daniel Lezcano
2015-10-29 22:52 ` [PATCH 5/7] clocksource/drivers/pxa_timer: Move the Kconfig rule Daniel Lezcano
2015-10-29 22:52 ` [PATCH 6/7] clocksource/drivers/pxa_timer: Add the COMPILE_TEST option Daniel Lezcano
2015-10-30 6:12 ` kbuild test robot
2015-10-29 22:52 ` Daniel Lezcano [this message]
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=1446159166-20384-7-git-send-email-daniel.lezcano@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome