From: "tip-bot2 for Daniel Lezcano" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: timers/core] clocksource/drivers/tegra186: Put Kconfig option 'tristate' to 'bool'
Date: Thu, 28 Jul 2022 10:44:03 -0000 [thread overview]
Message-ID: <165900504361.15455.7202765072349365466.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20220718213657.1303538-1-daniel.lezcano@linaro.org>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 110a25357584a2d2d9f50accb1e89455c54290b6
Gitweb: https://git.kernel.org/tip/110a25357584a2d2d9f50accb1e89455c54290b6
Author: Daniel Lezcano <daniel.lezcano@linaro.org>
AuthorDate: Mon, 18 Jul 2022 23:36:57 +02:00
Committer: Daniel Lezcano <daniel.lezcano@linaro.org>
CommitterDate: Wed, 27 Jul 2022 17:00:49 +02:00
clocksource/drivers/tegra186: Put Kconfig option 'tristate' to 'bool'
The clocksources are built-in, they are not modules. We don't know if
the core time framework is ready for clockevents / clocksources as
modules.
Revert back this option to 'bool'.
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20220718213657.1303538-1-daniel.lezcano@linaro.org
---
drivers/clocksource/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index 5d09cf5..440d4f4 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -158,7 +158,7 @@ config TEGRA_TIMER
Enables support for the Tegra driver.
config TEGRA186_TIMER
- tristate "NVIDIA Tegra186 timer driver"
+ bool "NVIDIA Tegra186 timer driver"
depends on ARCH_TEGRA || COMPILE_TEST
depends on WATCHDOG && WATCHDOG_CORE
help
prev parent reply other threads:[~2022-07-28 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 21:36 [PATCH] " Daniel Lezcano
2022-07-20 10:25 ` Daniel Lezcano
2022-07-28 10:44 ` tip-bot2 for 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=165900504361.15455.7202765072349365466.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®