From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Remove ARCH_HAS_CPUFREQ config option
Date: Tue, 03 Jun 2014 11:11:46 -0700 [thread overview]
Message-ID: <538E0FE2.4090405@codeaurora.org> (raw)
In-Reply-To: <CAOh2x==wsy2_+GygS03snFN_YOar3eHi7v1a-jNdsQYoWCAZsw@mail.gmail.com>
On 06/02/14 21:27, Viresh Kumar wrote:
> On Tue, Jun 3, 2014 at 3:37 AM, Stephen Boyd <sboyd@codeaurora.org> wrote:
>> This config exists entirely to hide the cpufreq menu from the
>> kernel configuration unless a platform has selected it. Nothing
>> is actually built if this config is 'Y' and it just leads to
>> more patches that add a select under a platform Kconfig so that
>> some other CPUfreq option can be chosen. Let's remove the
>> option so that we can always enable CPUfreq drivers on ARM
>> platforms.
>>
>> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
>> ---
>> arch/arm/Kconfig | 18 ------------------
>> arch/arm/mach-davinci/Kconfig | 1 -
>> arch/arm/mach-highbank/Kconfig | 1 -
>> arch/arm/mach-imx/Kconfig | 3 ---
>> arch/arm/mach-mvebu/Kconfig | 1 -
>> arch/arm/mach-omap2/Kconfig | 1 -
>> arch/arm/mach-shmobile/Kconfig | 2 --
>> arch/arm/mach-spear/Kconfig | 1 -
>> arch/arm/mach-tegra/Kconfig | 1 -
>> arch/arm/mach-ux500/Kconfig | 1 -
>> arch/arm/mach-vexpress/Kconfig | 1 -
>> arch/arm/mach-vt8500/Kconfig | 1 -
>> arch/arm/mach-zynq/Kconfig | 1 -
>> 13 files changed, 33 deletions(-)
> Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> While you are at it, please see if you can also fix unicore as well.
Sure I'll send a separate patch and Cc you.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2014-06-03 18:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 22:07 [PATCH] ARM: Remove ARCH_HAS_CPUFREQ config option Stephen Boyd
2014-06-03 4:27 ` Viresh Kumar
2014-06-03 18:11 ` Stephen Boyd [this message]
2014-06-03 6:13 ` Sachin Kamat
2014-06-03 18:11 ` 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=538E0FE2.4090405@codeaurora.org \
--to=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).