From: Arnd Bergmann <arnd@arndb•de>
To: Viresh Kumar <viresh.kumar@linaro•org>
Cc: robin.randhawa@arm•com, linux-pm@vger•kernel.org,
patches@linaro•org, Liviu.Dudau@arm•com,
linux-kernel@vger•kernel.org, cpufreq@vger•kernel.org,
rjw@sisk•pl, Steve.Bannister@arm•com, arvind.chauhan@arm•com,
linuxppc-dev@lists•ozlabs.org, linaro-kernel@lists•linaro.org,
charles.garcia-tobin@arm•com
Subject: Re: [PATCH 18/18] cpufreq: powerpc/platforms/cell: move cpufreq driver to drivers/cpufreq
Date: Thu, 4 Apr 2013 14:48:10 +0000 [thread overview]
Message-ID: <201304041448.11052.arnd@arndb.de> (raw)
In-Reply-To: <CAKohpok_ftPoME0tFRMWMM9A2mNSOpQSvbJut0=AzhCuB-Yjrg@mail.gmail.com>
On Thursday 04 April 2013, Viresh Kumar wrote:
>
> On 4 April 2013 18:32, Arnd Bergmann <arnd@arndb•de> wrote:
> > Moving the files is good, but I don't see a reason to make the cbe_cpufreq.h
> > header globally visible in include/linux/. Isn't it just used by as the
> > interface between ppc_cbe_cpufreq_pmi.c and ppc_cbe_cpufreq.c?
>
> When i moved it initially i thought it is also used by
> arch/powerpc/platforms/cell/cpufreq_spudemand.c and hence moved it
> to include/linux and never realized i am wrong..
>
> Here is the fixup (And attached complete patch: original+fixup for Rafael
> to apply):
Acked-by: Arnd Bergmann <arnd@arndb•de>
prev parent reply other threads:[~2013-04-04 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1365079581.git.viresh.kumar@linaro.org>
2013-04-04 12:54 ` [PATCH 17/18] cpufreq: powerpc: move cpufreq driver to drivers/cpufreq 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 [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=201304041448.11052.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=Liviu.Dudau@arm$(echo .)com \
--cc=Steve.Bannister@arm$(echo .)com \
--cc=arvind.chauhan@arm$(echo .)com \
--cc=charles.garcia-tobin@arm$(echo .)com \
--cc=cpufreq@vger$(echo .)kernel.org \
--cc=linaro-kernel@lists$(echo .)linaro.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-pm@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=patches@linaro$(echo .)org \
--cc=rjw@sisk$(echo .)pl \
--cc=robin.randhawa@arm$(echo .)com \
--cc=viresh.kumar@linaro$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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