From: Simon Horman <horms@verge.net.au>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, robin.randhawa@arm.com, Steve.Bannister@arm.com,
Liviu.Dudau@arm.com, charles.garcia-tobin@arm.com,
arvind.chauhan@arm.com, cpufreq@vger.kernel.org,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH 14/18] cpufreq: sh: move cpufreq driver to drivers/cpufreq
Date: Wed, 10 Apr 2013 11:12:36 +0900 [thread overview]
Message-ID: <20130410021236.GK11105@verge.net.au> (raw)
In-Reply-To: <CAKohpomqfVqiw1PJxBRRA8=A6hV_63AW4nRpM8TfZPA5bypcKQ@mail.gmail.com>
On Tue, Apr 09, 2013 at 07:42:51PM +0530, Viresh Kumar wrote:
> On 9 April 2013 18:25, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Apr 04, 2013 at 06:24:22PM +0530, Viresh Kumar wrote:
> >> This patch moves cpufreq driver of SUPERH architecture to drivers/cpufreq.
> >
> > Why?
> >
> > I am missing the cover email where I assume the explanation lies.
>
> Hi Simon,
>
> The idea was to keep all cpufreq drivers at a common and most suitable
> place, so that future consolidation work can be done easily and efficiently.
>
> So, functionally this patch shouldn't change anything.
Thanks, I understand.
I have no objections to this, but Paul should probably review it.
next prev parent reply other threads:[~2013-04-10 2:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 12:54 [PATCH 00/18] For-3.10: CPUFreq: Move drivers to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 01/18] cpufreq: ARM: Arrange drivers in alphabetical order Viresh Kumar
2013-04-04 12:54 ` [PATCH 02/18] cpufreq: tegra: Move driver to drivers/cpufreq Viresh Kumar
2013-04-04 12:54 ` [PATCH 03/18] cpufreq: davinci: move cpufreq " Viresh Kumar
2013-04-04 12:54 ` [PATCH 04/18] cpufreq: pxa3xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 05/18] cpufreq: pxa2xx: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 06/18] cpufreq: integrator: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 07/18] cpufreq: s3c24xx: " Viresh Kumar
2013-04-05 6:48 ` Kukjin Kim
2013-04-05 7:06 ` Viresh Kumar
2013-04-05 11:36 ` Rafael J. Wysocki
2013-04-08 9:15 ` Kukjin Kim
2013-04-08 9:18 ` Viresh Kumar
2013-04-08 10:46 ` Rafael J. Wysocki
2013-04-08 10:41 ` Kukjin Kim
2013-04-23 15:25 ` Kukjin Kim
2013-04-23 22:59 ` Rafael J. Wysocki
2013-04-25 16:48 ` Kukjin Kim
2013-04-25 18:12 ` Rafael J. Wysocki
2013-05-13 6:05 ` Viresh Kumar
2013-05-13 10:51 ` Rafael J. Wysocki
2013-05-13 10:46 ` Viresh Kumar
2013-05-14 12:36 ` Kukjin Kim
2013-05-14 13:00 ` Rafael J. Wysocki
2013-05-20 5:29 ` Viresh Kumar
2013-05-20 13:47 ` Kukjin Kim
2013-04-08 4:54 ` Viresh Kumar
2013-04-04 12:54 ` [PATCH 08/18] cpufreq: sa11x0: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 09/18] cpufreq: AVR32: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 10/18] cpufreq: blackfin: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 11/18] cpufreq: cris: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 12/18] cpufreq: ia64: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 13/18] cpufreq: mips: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 14/18] cpufreq: sh: " Viresh Kumar
2013-04-09 12:55 ` Simon Horman
2013-04-09 14:12 ` Viresh Kumar
2013-04-10 2:12 ` Simon Horman [this message]
2013-04-10 2:51 ` Viresh Kumar
2013-04-10 4:30 ` Simon Horman
2013-04-04 12:54 ` [PATCH 15/18] cpufreq: unicore2: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 16/18] cpufreq: sparc: " Viresh Kumar
2013-04-04 12:54 ` [PATCH 17/18] cpufreq: powerpc: " Viresh Kumar
2013-04-05 6:46 ` Viresh Kumar
2013-04-09 8:35 ` Viresh Kumar
2013-04-22 6:49 ` Viresh Kumar
2013-05-13 6:04 ` Viresh Kumar
2013-05-20 4:40 ` Viresh Kumar
2013-05-31 10:50 ` Viresh Kumar
2013-06-07 5:18 ` Viresh Kumar
2013-06-07 11:58 ` Rafael J. Wysocki
2013-04-04 12:54 ` [PATCH 18/18] cpufreq: powerpc/platforms/cell: " Viresh Kumar
2013-04-04 13:02 ` Arnd Bergmann
2013-04-04 13:50 ` Viresh Kumar
2013-04-04 14:48 ` Arnd Bergmann
2013-04-04 22:36 ` [PATCH 00/18] For-3.10: CPUFreq: Move drivers " Rafael J. Wysocki
2013-04-05 1:17 ` 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=20130410021236.GK11105@verge.net.au \
--to=horms@verge.net.au \
--cc=Liviu.Dudau@arm.com \
--cc=Steve.Bannister@arm.com \
--cc=arvind.chauhan@arm.com \
--cc=charles.garcia-tobin@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=lethal@linux-sh.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=patches@linaro.org \
--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).