From: Jean Delvare <jdelvare@suse.de>
To: linux-clk@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Peter Collingbourne <pcc@google.com>,
Lee Jones <lee.jones@linaro.org>
Subject: [PATCH 2/2] clk: versatile: hide clock drivers from non-ARM users
Date: Wed, 1 Sep 2021 18:09:53 +0200 [thread overview]
Message-ID: <20210901180953.5bd2a994@endymion> (raw)
In-Reply-To: <20210901180833.4558932d@endymion>
Commit 419b3ab6987f ("clk: versatile: remove dependency on ARCH_*")
made the whole menu of ARM reference clock drivers visible on all
architectures. I can't see how this is an improvement for non-ARM
users. Unless build-testing, there is no point on presenting
ARM-only clock drivers on other architectures.
Signed-off-by: Jean Delvare <jdelvare@suse.de>
Cc: Peter Collingbourne <pcc@google.com>
Cc: Lee Jones <lee.jones@linaro.org>
Cc: Linus Walleij <linus.walleij@linaro.org>
Cc: Stephen Boyd <sboyd@kernel.org>
---
drivers/clk/versatile/Kconfig | 1 +
1 file changed, 1 insertion(+)
--- linux-5.14.orig/drivers/clk/versatile/Kconfig 2021-09-01 17:28:15.853037684 +0200
+++ linux-5.14/drivers/clk/versatile/Kconfig 2021-09-01 17:32:58.498817653 +0200
@@ -2,6 +2,7 @@
menu "Clock driver for ARM Reference designs"
depends on HAS_IOMEM
+ depends on ARM || ARM64 || COMPILE_TEST
config CLK_ICST
bool "Clock driver for ARM Reference designs ICST"
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2021-09-01 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 16:08 [PATCH 1/2] clk: versatile: Rename ICST to CLK_ICST Jean Delvare
2021-09-01 16:09 ` Jean Delvare [this message]
2021-09-16 23:01 ` [PATCH 2/2] clk: versatile: hide clock drivers from non-ARM users Linus Walleij
2021-10-15 1:01 ` Stephen Boyd
2021-09-16 23:00 ` [PATCH 1/2] clk: versatile: Rename ICST to CLK_ICST Linus Walleij
2021-10-15 1:00 ` Stephen Boyd
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=20210901180953.5bd2a994@endymion \
--to=jdelvare@suse.de \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=pcc@google.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.