From: Andrew Lunn <andrew@lunn.ch>
To: Quentin Armitage <quentin@armitage.org.uk>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH] cpufreq: kirkwood: Reinstate cpufreq driver for ARCH_KIRKWOOD
Date: Thu, 10 Jul 2014 15:58:59 +0200 [thread overview]
Message-ID: <20140710135859.GL21833@lunn.ch> (raw)
In-Reply-To: <1404987355.23201.65.camel@samson1.armitage.org.uk>
On Thu, Jul 10, 2014 at 11:15:55AM +0100, Quentin Armitage wrote:
> Commit ff1f0018cf66080d8e6f59791e552615648a033a ("drivers: Enable
> building of Kirkwood drivers for mach-mvebu") added Kirkwood into
> mach-mvebu, adding MACH_KIRKWOOD to ARCH_KIRKWOOD in the KConfig files.
>
> The change for ARM_KIRKWOOD_CPUFREQ replaced ARCH_KIRKWOOD with
> MACH_KIRKWOOD, whereas all the other changes were ARCH_KIRKWOOD ||
> MACH_KIRKWOOD.
>
> As a consequence of this change, the cpufreq driver is no longer enabled
> for ARCH_KIRKWOOD. This patch reinstates ARM_KIRKWOOD_CPUFREQ for
> ARCH_KIRKWOOD.
>
> Signed-off-by: Quentin Armitage <quentin@armitage.org.uk>
> ---
> diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm
> index ebac671..24778f0 100644
> --- a/drivers/cpufreq/Kconfig.arm
> +++ b/drivers/cpufreq/Kconfig.arm
> @@ -118,7 +118,7 @@ config ARM_INTEGRATOR
> If in doubt, say Y.
>
> config ARM_KIRKWOOD_CPUFREQ
> - def_bool MACH_KIRKWOOD
> + def_bool ARCH_KIRKWOOD || MACH_KIRKWOOD
> help
> This adds the CPUFreq driver for Marvell Kirkwood
> SoCs.
Acked-by: Andrew Lunn <andrew@lunn.ch>
Andrew
next prev parent reply other threads:[~2014-07-10 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 10:15 [PATCH] cpufreq: kirkwood: Reinstate cpufreq driver for ARCH_KIRKWOOD Quentin Armitage
2014-07-10 10:20 ` Viresh Kumar
2014-07-10 13:58 ` Andrew Lunn [this message]
2014-07-18 1:08 ` 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=20140710135859.GL21833@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quentin@armitage.org.uk \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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.