From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: linux-rtc@vger.kernel.org,
Alessandro Zummo <a.zummo@towertech.it>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 02/21] rtc: armada38x: depend on OF
Date: Tue, 2 Feb 2021 12:21:59 +0100 [thread overview]
Message-ID: <20210202112219.3610853-3-alexandre.belloni@bootlin.com> (raw)
In-Reply-To: <20210202112219.3610853-1-alexandre.belloni@bootlin.com>
The driver will compile with warning without OF because armada38x_data and
armada8k_data will be defined but not used. It would be possible to move
then in the #ifdef CONFIG_OF section but then their members will be defined
but not used. Instead of moving most of the driver in the #ifdef, simply
depend on OF.
Signed-off-by: Alexandre Belloni <alexandre.belloni@bootlin.com>
---
drivers/rtc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/rtc/Kconfig b/drivers/rtc/Kconfig
index e1576754a50f..68ae202e0716 100644
--- a/drivers/rtc/Kconfig
+++ b/drivers/rtc/Kconfig
@@ -1594,6 +1594,7 @@ config RTC_DRV_MV
config RTC_DRV_ARMADA38X
tristate "Armada 38x Marvell SoC RTC"
depends on ARCH_MVEBU || COMPILE_TEST
+ depends on OF
help
If you say yes here you will get support for the in-chip RTC
that can be found in the Armada 38x Marvell's SoC device
--
2.29.2
next prev parent reply other threads:[~2021-02-02 11:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 11:21 [PATCH 00/21] rtc: remove make W=1 warnings Alexandre Belloni
2021-02-02 11:21 ` [PATCH 01/21] rtc: class: remove bogus documentation Alexandre Belloni
2021-02-02 11:21 ` Alexandre Belloni [this message]
2021-02-02 11:22 ` [PATCH 03/21] rtc: bq32k: quiet maybe-unused variable warning Alexandre Belloni
2021-02-02 11:22 ` [PATCH 04/21] rtc: brcmstb-waketimer: " Alexandre Belloni
2021-02-02 17:22 ` Florian Fainelli
2021-02-02 17:23 ` Florian Fainelli
2021-02-02 11:22 ` [PATCH 05/21] rtc: digicolor: " Alexandre Belloni
2021-02-02 11:32 ` Baruch Siach
2021-02-02 11:22 ` [PATCH 06/21] rtc: ds1672: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 07/21] rtc: ds3232: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 08/21] rtc: isl1208: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 09/21] rtc: m41t80: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 10/21] rtc: meson: " Alexandre Belloni
2021-02-02 16:26 ` Kevin Hilman
2021-02-02 11:22 ` [PATCH 11/21] rtc: pcf85063: quiet maybe-unused variable warnings Alexandre Belloni
2021-02-02 11:22 ` [PATCH 12/21] rtc: pcf85363: quiet maybe-unused variable warning Alexandre Belloni
2021-02-02 11:22 ` [PATCH 13/21] rtc: rs5c372: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 14/21] rtc: rv3028: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 15/21] rtc: rv3029: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 16/21] rtc: rv3032: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 17/21] rtc: rv8803: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 18/21] rtc: rx8010: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 19/21] rtc: rx8581: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 20/21] rtc: s35390a: " Alexandre Belloni
2021-02-02 11:22 ` [PATCH 21/21] rtc: sd3078: " Alexandre Belloni
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=20210202112219.3610853-3-alexandre.belloni@bootlin.com \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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;
as well as URLs for NNTP newsgroup(s).