From: Eric Miao <eric.y.miao@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Haojian Zhuang <haojian.zhuang@gmail.com>,
"arvind.chauhan" <arvind.chauhan@arm.com>,
"robin.randhawa" <robin.randhawa@arm.com>,
"steve.bannister" <Steve.Bannister@arm.com>,
"liviu.dudau" <Liviu.Dudau@arm.com>,
"charles.garcia-tobin" <charles.garcia-tobin@arm.com>,
cpufreq <cpufreq@vger.kernel.org>,
linux-pm <linux-pm@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
linaro-kernel@lists.linaro.org,
Arnd Bergmann <arnd.bergmann@linaro.org>,
Russell King <linux@arm.linux.org.uk>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: [PATCH 6/9] cpufreq: pxa3xx: move cpufreq driver to drivers/cpufreq
Date: Sun, 31 Mar 2013 19:34:34 +0800 [thread overview]
Message-ID: <CAMPhdO_ix16iy+KX+pXwhpO4u3Lx_eL3vVCyf+Lu4HthodekRA@mail.gmail.com> (raw)
In-Reply-To: <CAKohpok6vQtbHC0u+XCbPLyJf3w=v=LUNqZB2eJ5msy7=3zWgA@mail.gmail.com>
On Sun, Mar 31, 2013 at 2:45 PM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> On 31 March 2013 10:54, Eric Miao <eric.y.miao@gmail.com> wrote:
>> On Sun, Mar 31, 2013 at 11:52 AM, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>>> Eric/Haojian,
>>>
>>> On 25 March 2013 15:41, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>>>> This patch moves cpufreq driver of ARM based pxa3xx platform to drivers/cpufreq.
>>>>
>>>> Cc: Eric Miao <eric.y.miao@gmail.com>
>>
>> Acked-by: Eric Miao <eric.y.miao@gmail.com>
>>
>>>> Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
>>>> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>>>> ---
>>>> arch/arm/mach-pxa/Makefile | 1 -
>>>> arch/arm/mach-pxa/include/mach/generic.h | 1 +
>>>> drivers/cpufreq/Makefile | 1 +
>>>> .../mach-pxa/cpufreq-pxa3xx.c => drivers/cpufreq/pxa3xx-cpufreq.c | 5 +----
>>>> 4 files changed, 3 insertions(+), 5 deletions(-)
>>>> create mode 100644 arch/arm/mach-pxa/include/mach/generic.h
>>>> rename arch/arm/mach-pxa/cpufreq-pxa3xx.c => drivers/cpufreq/pxa3xx-cpufreq.c (98%)
>>>
>>> Can i have your Ack or views about 6/9 and 7/9 Patch?
>
> Is this for both the patches??
Yes. Take the Ack for both, those two should really belong to drivers/cpufreq.
next prev parent reply other threads:[~2013-03-31 11:34 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 10:11 [PATCH 0/9] ARM: CPUFreq: Move drivers arch/arm/ -> drivers/cpufreq Viresh Kumar
2013-03-25 10:11 ` [PATCH 1/9] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-03-25 10:11 ` [PATCH 2/9] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-03-25 10:11 ` [PATCH 3/9] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-03-27 10:17 ` Sekhar Nori
2013-03-27 10:21 ` Viresh Kumar
2013-03-27 10:32 ` Sekhar Nori
2013-03-27 10:37 ` Viresh Kumar
2013-03-27 10:56 ` Sekhar Nori
2013-03-25 10:11 ` [PATCH 4/9] cpufreq: imx: " Viresh Kumar
2013-03-27 15:22 ` Markus Pargmann
2013-03-27 15:23 ` Viresh Kumar
2013-03-25 10:11 ` [PATCH 5/9] cpufreq: integrator: " Viresh Kumar
2013-03-31 3:51 ` Viresh Kumar
2013-04-04 8:32 ` Viresh Kumar
2013-04-04 11:40 ` Linus Walleij
2013-03-25 10:11 ` [PATCH 6/9] cpufreq: pxa3xx: " Viresh Kumar
2013-03-31 3:52 ` Viresh Kumar
2013-03-31 5:24 ` Eric Miao
2013-03-31 6:45 ` Viresh Kumar
2013-03-31 11:34 ` Eric Miao [this message]
2013-03-25 10:11 ` [PATCH 7/9] cpufreq: pxa2xx: " Viresh Kumar
2013-03-25 10:11 ` [PATCH 8/9] cpufreq: s3c24xx: " Viresh Kumar
2013-03-31 3:53 ` Viresh Kumar
2013-04-03 9:27 ` Viresh Kumar
2013-03-25 10:11 ` [PATCH 9/9] cpufreq: sa11x0: " Viresh Kumar
2013-03-31 3:54 ` Viresh Kumar
2013-03-25 10:33 ` [PATCH 0/9] ARM: CPUFreq: Move drivers arch/arm/ -> drivers/cpufreq Viresh Kumar
2013-03-25 16:49 ` Stephen Warren
2013-04-04 9:38 ` Arnd Bergmann
2013-04-04 9:39 ` 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=CAMPhdO_ix16iy+KX+pXwhpO4u3Lx_eL3vVCyf+Lu4HthodekRA@mail.gmail.com \
--to=eric.y.miao@gmail.com \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arnd.bergmann@linaro.org \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=haojian.zhuang@gmail.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=rjw@sisk.pl \
--cc=robin.randhawa@arm.com \
--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 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).