From: "tip-bot2 for Johan Hovold" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Johan Hovold <johan@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>, x86 <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: [tip: timers/core] clocksource/drivers/rda: drop redundant Kconfig dependency
Date: Mon, 01 Jun 2020 13:11:45 -0000 [thread overview]
Message-ID: <159101710552.17951.6306013470249214753.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20200513122548.16974-1-johan@kernel.org>
The following commit has been merged into the timers/core branch of tip:
Commit-ID: 83cba9536905e4f82b726a98fe404400f0c9eb76
Gitweb: https://git.kernel.org/tip/83cba9536905e4f82b726a98fe404400f0c9eb76
Author: Johan Hovold <johan@kernel.org>
AuthorDate: Wed, 13 May 2020 14:25:48 +02:00
Committer: Daniel Lezcano <daniel.lezcano@linaro.org>
CommitterDate: Fri, 22 May 2020 23:58:56 +02:00
clocksource/drivers/rda: drop redundant Kconfig dependency
Since commit 2f8a26c166eb ("clocksource: Improve GENERIC_CLOCKEVENTS
dependency") all clocksource drivers depend on GENERIC_CLOCKEVENTS so
drop the redundant attribute from the RDA-timer entry which was added
later.
Signed-off-by: Johan Hovold <johan@kernel.org>
Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
Link: https://lore.kernel.org/r/20200513122548.16974-1-johan@kernel.org
---
drivers/clocksource/Kconfig | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/clocksource/Kconfig b/drivers/clocksource/Kconfig
index 9c2d72b..c824002 100644
--- a/drivers/clocksource/Kconfig
+++ b/drivers/clocksource/Kconfig
@@ -120,7 +120,6 @@ config OWL_TIMER
config RDA_TIMER
bool "RDA timer driver" if COMPILE_TEST
- depends on GENERIC_CLOCKEVENTS
select CLKSRC_MMIO
select TIMER_OF
help
prev parent reply other threads:[~2020-06-01 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 12:25 [PATCH] " Johan Hovold
2020-05-18 14:10 ` Daniel Lezcano
2020-06-01 13:11 ` tip-bot2 for Johan Hovold [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=159101710552.17951.6306013470249214753.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=daniel.lezcano@linaro.org \
--cc=johan@kernel.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®