From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] Enable Calxeda cpufreq driver on arm64
Date: Wed, 4 Dec 2013 18:23:12 -0600 [thread overview]
Message-ID: <1386202994-30784-1-git-send-email-robherring2@gmail.com> (raw)
From: Rob Herring <rob.herring@calxeda.com>
This series enables cpufreq subsystem and the highbank-cpufreq driver
for arm64. Nothing more really than sorting kconfig options to allow
the driver to build. There's no reason for the driver to depend on
ARCH_HIGHBANK and I'm trying to avoid adding that (or a new option)
for arm64.
Rob
Rob Herring (2):
cpufreq: enable ARM drivers on arm64
cpufreq: highbank: rework the kconfig dependencies for arm64
arch/arm64/Kconfig | 8 ++++++++
drivers/cpufreq/Kconfig | 2 +-
drivers/cpufreq/Kconfig.arm | 14 ++++++--------
3 files changed, 15 insertions(+), 9 deletions(-)
--
1.8.3.2
next reply other threads:[~2013-12-05 0:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-05 0:23 Rob Herring [this message]
2013-12-05 0:23 ` [PATCH 1/2] cpufreq: enable ARM drivers on arm64 Rob Herring
2013-12-05 18:16 ` Mark Brown
2013-12-05 20:03 ` Rob Herring
2013-12-05 20:35 ` Mark Brown
2013-12-05 0:23 ` [PATCH 2/2] cpufreq: highbank: rework the kconfig dependencies for arm64 Rob Herring
2013-12-16 8:54 ` Viresh Kumar
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=1386202994-30784-1-git-send-email-robherring2@gmail.com \
--to=robherring2@gmail.com \
--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).