From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep.KarkadaNagesha@arm.com
Cc: linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, cpufreq@vger.kernel.org,
arnd@arndb.de, olof@lixom.net, lorenzo.pieralisi@arm.com,
rob.herring@calxeda.com, grant.likely@linaro.org, rjw@sisk.pl,
gregkh@linuxfoundation.org, gregory.clement@free-electrons.com,
kernel@pengutronix.de, shawn.guo@linaro.org,
linux@arm.linux.org.uk
Subject: Re: [RFC PATCH 00/11] ARM: DT: update cpu device of_node
Date: Tue, 16 Jul 2013 12:01:37 +0530 [thread overview]
Message-ID: <CAKohponiPd6YZFiQGY3UXdtb0WDWsqsPoZJ-53z6Qjm4e7ap_w@mail.gmail.com> (raw)
In-Reply-To: <1373883732-26303-1-git-send-email-Sudeep.KarkadaNagesha@arm.com>
On 15 July 2013 15:52, <Sudeep.KarkadaNagesha@arm.com> wrote:
> Sudeep KarkadaNagesha (11):
> cpufreq: imx6q-cpufreq: remove device tree parsing for cpu nodes
> cpufreq: cpufreq-cpu0: remove device tree parsing for cpu nodes
> cpufreq: highbank-cpufreq: remove device tree parsing for cpu nodes
> cpufreq: spear-cpufreq: remove device tree parsing for cpu nodes
> cpufreq: kirkwood-cpufreq: remove device tree parsing for cpu nodes
> cpufreq: arm_big_little: remove device tree parsing for cpu nodes
For cpufreq part:
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
prev parent reply other threads:[~2013-07-16 6:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-15 10:22 [RFC PATCH 00/11] ARM: DT: update cpu device of_node Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 01/11] driver/core: cpu: initialize of_node in cpu's device struture Sudeep.KarkadaNagesha
2013-07-16 6:27 ` Viresh Kumar
2013-07-15 10:22 ` [RFC PATCH 02/11] ARM: DT/kernel: define ARM specific arch_of_get_cpu_node Sudeep.KarkadaNagesha
2013-07-15 19:10 ` Rob Herring
2013-07-16 6:29 ` Viresh Kumar
2013-07-16 9:03 ` Sudeep KarkadaNagesha
2013-07-17 14:16 ` Sudeep KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 03/11] ARM: topology: remove hwid/MPIDR dependency from cpu_capacity Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 04/11] ARM: mvebu: remove device tree parsing for cpu nodes Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 05/11] drivers/bus: arm-cci: avoid parsing DT for cpu device nodes Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 06/11] cpufreq: imx6q-cpufreq: remove device tree parsing for cpu nodes Sudeep.KarkadaNagesha
2013-07-16 1:22 ` Shawn Guo
2013-07-15 10:22 ` [RFC PATCH 07/11] cpufreq: cpufreq-cpu0: " Sudeep.KarkadaNagesha
2013-07-16 1:26 ` Shawn Guo
2013-07-15 10:22 ` [RFC PATCH 08/11] cpufreq: highbank-cpufreq: " Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 09/11] cpufreq: spear-cpufreq: " Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 10/11] cpufreq: kirkwood-cpufreq: " Sudeep.KarkadaNagesha
2013-07-15 10:22 ` [RFC PATCH 11/11] cpufreq: arm_big_little: " Sudeep.KarkadaNagesha
2013-07-16 6:31 ` Viresh Kumar [this message]
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=CAKohponiPd6YZFiQGY3UXdtb0WDWsqsPoZJ-53z6Qjm4e7ap_w@mail.gmail.com \
--to=viresh.kumar@linaro.org \
--cc=Sudeep.KarkadaNagesha@arm.com \
--cc=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@free-electrons.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=olof@lixom.net \
--cc=rjw@sisk.pl \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@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 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).