From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] cpufreq: OMAP: fix build errors: depends on ARCH_OMAP2PLUS
Date: Wed, 04 Apr 2012 15:20:22 -0700 [thread overview]
Message-ID: <4F7CC926.5050300@ti.com> (raw)
In-Reply-To: <1332807568-638-1-git-send-email-khilman@ti.com>
Hi Dave,
On 03/26/2012 05:19 PM, Kevin Hilman wrote:
> The OMAP driver needs a 'depends on ARCH_OMAP2PLUS' since it only
> builds for OMAP2+ platforms.
>
> This 'depends on' was in the original patch from Russell King, but was
> erroneously removed by me when making this option user-selectable in
> commit b09db45c (cpufreq: OMAP driver depends CPUfreq tables.) This
> patch remedies that.
>
> Apologies to Russell King for breaking his originally working patch.
>
> Also, thanks to Grazvydas Ignotas for reporting the same problem.
>
> Cc: Russell King<rmk+kernel@arm•linux.org.uk>
> Cc: Grazvydas Ignotas<notasas@gmail•com>
> Signed-off-by: Kevin Hilman<khilman@ti•com>
> ---
> Dave, this applies on top of your current fixes branch, and fixes a
> problem introduced there by me. Please merge for v3.4-rc. Thanks.
Can you pick this up for v3.4-rc?
Thanks,
Kevin
> drivers/cpufreq/Kconfig.arm | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index 82f1aa9..555a57b 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -4,6 +4,7 @@
>
> config ARM_OMAP2PLUS_CPUFREQ
> bool "TI OMAP2+"
> + depends on ARCH_OMAP2PLUS
> default ARCH_OMAP2PLUS
> select CPU_FREQ_TABLE
>
next prev parent reply other threads:[~2012-04-04 22:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 0:19 [PATCH] cpufreq: OMAP: fix build errors: depends on ARCH_OMAP2PLUS Kevin Hilman
2012-03-30 13:12 ` Russell King - ARM Linux
2012-03-30 14:24 ` Kevin Hilman
2012-04-04 22:20 ` Kevin Hilman [this message]
2012-04-13 18:53 ` Russell King - ARM Linux
2012-04-13 21:31 ` Kevin Hilman
-- strict thread matches above, loose matches on Subject: below --
2012-04-13 20:32 Kevin Hilman
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=4F7CC926.5050300@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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