[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <538E0FE2.4090405@codeaurora.org>
Date: Tue, 03 Jun 2014 11:11:46 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
CC: "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"arm@...nel.org" <arm@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ARM: Remove ARCH_HAS_CPUFREQ config option
On 06/02/14 21:27, Viresh Kumar wrote:
> On Tue, Jun 3, 2014 at 3:37 AM, Stephen Boyd <sboyd@...eaurora.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@...eaurora.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@...aro.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists