From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] cpufreq: qoriq: allow building as module with THERMAL=m
Date: Mon, 29 Feb 2016 21:56:11 +0530 [thread overview]
Message-ID: <20160229162611.GU2791@vireshk-i7> (raw)
In-Reply-To: <1456761867-1742824-1-git-send-email-arnd@arndb.de>
On 29-02-16, 17:04, Arnd Bergmann wrote:
> My previous patch to avoid link errors with the qoriq cpufreq
> driver disallowed all of the broken cases, but also prevented
> the driver from being built when CONFIG_THERMAL is a module.
>
> This changes the dependency to allow the cpufreq driver to
> also be a module in this case, just not built-in.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> Fixes: cpufreq: qoriq depends on thermal
> ---
>
> If possible, please fold this change directly into the previous
> commit
>
> drivers/cpufreq/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/cpufreq/Kconfig b/drivers/cpufreq/Kconfig
> index ca05037dd565..d5e11d24f72b 100644
> --- a/drivers/cpufreq/Kconfig
> +++ b/drivers/cpufreq/Kconfig
> @@ -297,7 +297,7 @@ endif
> config QORIQ_CPUFREQ
> tristate "CPU frequency scaling driver for Freescale QorIQ SoCs"
> depends on OF && COMMON_CLK && (PPC_E500MC || ARM)
> - depends on !CPU_THERMAL || THERMAL=y
> + depends on !CPU_THERMAL || THERMAL
> select CLK_QORIQ
> help
> This adds the CPUFreq driver support for Freescale QorIQ SoCs
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2016-02-29 16:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:04 [PATCH 1/2] cpufreq: qoriq: allow building as module with THERMAL=m Arnd Bergmann
2016-02-29 16:04 ` [PATCH 2/2] cpufreq: mediatek: allow building as a module Arnd Bergmann
2016-03-01 15:04 ` Matthias Brugger
2016-02-29 16:26 ` Viresh Kumar [this message]
2016-03-01 2:00 ` [PATCH 1/2] cpufreq: qoriq: allow building as module with THERMAL=m Rafael J. Wysocki
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=20160229162611.GU2791@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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