All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: rjw@sisk.pl, arvind.chauhan@arm.com, robin.randhawa@arm.com,
	Steve.Bannister@arm.com, Liviu.Dudau@arm.com,
	charles.garcia-tobin@arm.com, cpufreq@vger.kernel.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linaro-kernel@lists.linaro.org, arnd.bergmann@linaro.org,
	linux@arm.linux.org.uk
Subject: Re: [PATCH 0/9] ARM: CPUFreq: Move drivers arch/arm/ -> drivers/cpufreq
Date: Mon, 25 Mar 2013 10:49:45 -0600	[thread overview]
Message-ID: <51508029.6050801@wwwdotorg.org> (raw)
In-Reply-To: <cover.1364205812.git.viresh.kumar@linaro.org>

On 03/25/2013 04:11 AM, Viresh Kumar wrote:
> Hi,
> 
> This patchset tries to move all CPUFreq drivers for ARM platforms from arch/arm
> to drivers/cpufreq directory.
> 
> This series is dependent (rebased of) on following patches:
> 
> http://www.spinics.net/lists/arm-kernel/msg232540.html
> https://lkml.org/lkml/2013/3/24/151
> 
> I want this series to go through Rafael's tree due to dependencies and so want
> Ack's by respective maintainers.

Patches 1 and 2,

Acked-by: Stephen Warren <swarren@nvidia.com>
Tested-by: Stephen Warren <swarren@nvidia.com>

On Tegra.

  parent reply	other threads:[~2013-03-25 16:49 UTC|newest]

Thread overview: 34+ 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:17     ` Sekhar Nori
2013-03-27 10:21     ` Viresh Kumar
2013-03-27 10:32       ` Sekhar Nori
2013-03-27 10:32         ` Sekhar Nori
2013-03-27 10:37         ` Viresh Kumar
2013-03-27 10:56       ` Sekhar Nori
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
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 [this message]
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=51508029.6050801@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.