From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>, Chen-Yu Tsai <wens@csie.org>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
arnd.bergmann@linaro.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/8] cpufreq: sunxi: Use generic platdev driver
Date: Thu, 21 Apr 2016 10:54:02 +0200 [thread overview]
Message-ID: <20160421085402.GL13045@lukather> (raw)
In-Reply-To: <e82bf5994897cc979a67c72f09229b8b295bb69a.1461228081.git.viresh.kumar@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 554 bytes --]
On Thu, Apr 21, 2016 at 02:13:52PM +0530, Viresh Kumar wrote:
> The cpufreq-dt-platdev driver supports creation of cpufreq-dt platform
> device now, reuse that and remove similar code from platform code.
>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> Cc: Chen-Yu Tsai <wens@csie.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
Acked-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Thanks,
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-21 8:54 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 [this message]
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 ` [PATCH 0/8] cpufreq: dt: Don't create platform-device from platform code Arnd Bergmann
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=20160421085402.GL13045@lukather \
--to=maxime.ripard@free-electrons.com \
--cc=arnd.bergmann@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--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;
as well as URLs for NNTP newsgroup(s).