public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: linaro-kernel@lists.linaro.org
Cc: "Viresh Kumar" <viresh.kumar@linaro.org>,
	"Rafael Wysocki" <rjw@rjwysocki.net>,
	"Heiko Stuebner" <heiko@sntech.de>,
	linux-pm@vger.kernel.org, "Tony Lindgren" <tony@atomide.com>,
	"Antoine Tenart" <antoine.tenart@free-electrons.com>,
	"Magnus Damm" <magnus.damm@gmail.com>,
	"Michal Simek" <michal.simek@xilinx.com>,
	"Chen-Yu Tsai" <wens@csie.org>,
	"Simon Horman" <horms@verge.net.au>,
	"Sascha Hauer" <kernel@pengutronix.de>,
	"Leo Yan" <leo.yan@linaro.org>, "Shawn Guo" <shawnguo@kernel.org>,
	"Maxime Ripard" <maxime.ripard@free-electrons.com>,
	"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
	"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH 0/8] cpufreq: dt: Don't create platform-device from platform code
Date: Thu, 21 Apr 2016 11:49:49 +0200	[thread overview]
Message-ID: <4420115.OC4oi9pMlr@wuerfel> (raw)
In-Reply-To: <cover.1461228081.git.viresh.kumar@linaro.org>

On Thursday 21 April 2016 14:13:46 Viresh Kumar wrote:
> Hi,
> 
> This migrates rest of the platforms to use cpufreq-dt-platdev.c. There
> are few exceptions though:
> - mvebu: it uses platform data and its problem will be solved in a
>   separate series.
> - highbank, s5pv210, sti, tegra124: these platforms already have cpufreq
>   drivers in drivers/cpufreq/, which does some other stuff and finally
>   create the device. There are sequencing issues, and so they will be
>   left as it is.

Looks good overall, one minor comment for patch 3, thanks a lot for your
work on this!

Acked-by: Arnd Bergmann <arnd@arndb.de>


      parent reply	other threads:[~2016-04-21  9:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21  8:43 [PATCH 0/8] cpufreq: dt: Don't create platform-device from platform code Viresh Kumar
2016-04-21  8:43 ` [PATCH 1/8] cpufreq: berlin: Use generic platdev driver Viresh Kumar
2016-04-21  9:05   ` Antoine Tenart
2016-04-21  8:43 ` [PATCH 2/8] cpufreq: imx: " Viresh Kumar
2016-04-21  9:19   ` Lucas Stach
2016-04-21  9:46   ` Arnd Bergmann
2016-04-21  9:50     ` Viresh Kumar
2016-04-21 10:17       ` Arnd Bergmann
2016-04-21  8:43 ` [PATCH 3/8] cpufreq: omap: " Viresh Kumar
2016-04-21  8:43 ` [PATCH 4/8] cpufreq: rockchip: " Viresh Kumar
2016-04-21  8:43 ` [PATCH 5/8] cpufreq: shmobile: " Viresh Kumar
2016-04-21 13:04   ` Geert Uytterhoeven
2016-04-22  3:21     ` Viresh Kumar
2016-04-22  6:41       ` Geert Uytterhoeven
2016-04-22  6:47         ` Viresh Kumar
2016-04-21  8:43 ` [PATCH 6/8] cpufreq: sunxi: " Viresh Kumar
2016-04-21  8:54   ` Maxime Ripard
2016-04-21  8:43 ` [PATCH 7/8] cpufreq: zynq: " Viresh Kumar
2016-04-21  8:43 ` [PATCH 8/8] cpufreq: hisilicon: " Viresh Kumar
2016-04-23 17:14   ` Leo Yan
2016-04-21  9:49 ` 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=4420115.OC4oi9pMlr@wuerfel \
    --to=arnd@arndb.de \
    --cc=antoine.tenart@free-electrons.com \
    --cc=heiko@sntech.de \
    --cc=horms@verge.net.au \
    --cc=kernel@pengutronix.de \
    --cc=leo.yan@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=maxime.ripard@free-electrons.com \
    --cc=michal.simek@xilinx.com \
    --cc=rjw@rjwysocki.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=shawnguo@kernel.org \
    --cc=soren.brinkmann@xilinx.com \
    --cc=tony@atomide.com \
    --cc=viresh.kumar@linaro.org \
    --cc=wens@csie.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