From: John Crispin <john@phrozen.org>
To: viresh.kumar@linaro.org
Cc: linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH 5/9] mips: cpufreq: move cpufreq driver to drivers/cpufreq
Date: Wed, 03 Apr 2013 12:07:39 +0200 [thread overview]
Message-ID: <515BFF6B.3060000@phrozen.org> (raw)
In-Reply-To: <CAKohpome32G=Nn4Uy3kHJyeJ2cTUOBTwHy9nKo2r6Cb1=KVS7A@mail.gmail.com>
On 03/04/13 11:28, Viresh Kumar wrote:
> On 31 March 2013 09:31, Viresh Kumar<viresh.kumar@linaro.org> wrote:
>> On 25 March 2013 22:24, Viresh Kumar<viresh.kumar@linaro.org> wrote:
>>> This patch moves cpufreq driver of MIPS architecture to drivers/cpufreq.
>>>
>>> Cc: Ralf Baechle<ralf@linux-mips.org>
>>> Cc: linux-mips@linux-mips.org
>>> Signed-off-by: Viresh Kumar<viresh.kumar@linaro.org>
>>> ---
>>> arch/mips/Kconfig | 9 ++++-
>>> arch/mips/kernel/Makefile | 2 --
>>> arch/mips/kernel/cpufreq/Kconfig | 41 ----------------------
>>> arch/mips/kernel/cpufreq/Makefile | 5 ---
>>> drivers/cpufreq/Kconfig | 18 ++++++++++
>>> drivers/cpufreq/Makefile | 1 +
>>> .../kernel => drivers}/cpufreq/loongson2_cpufreq.c | 0
>>> 7 files changed, 27 insertions(+), 49 deletions(-)
>>> delete mode 100644 arch/mips/kernel/cpufreq/Kconfig
>>> delete mode 100644 arch/mips/kernel/cpufreq/Makefile
>>> rename {arch/mips/kernel => drivers}/cpufreq/loongson2_cpufreq.c (100%)
>>
>> Ralf or any other mips guy,
>>
>> Can i have your ack or comments for this patch?
>
> Ping!!
>
>
sorry for the delay ...
Acked-by: John Crispin <blogic@openwrt.org>
prev parent reply other threads:[~2013-04-03 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1364229828.git.viresh.kumar@linaro.org>
2013-03-25 16:54 ` [PATCH 5/9] mips: cpufreq: move cpufreq driver to drivers/cpufreq Viresh Kumar
2013-03-31 4:01 ` Viresh Kumar
2013-04-03 9:28 ` Viresh Kumar
2013-04-03 10:07 ` John Crispin [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=515BFF6B.3060000@phrozen.org \
--to=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--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