From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
arnd.bergmann@linaro.org, linaro-kernel@lists.linaro.org,
linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [PATCH 2/8] cpufreq: imx: Use generic platdev driver
Date: Thu, 21 Apr 2016 11:46:59 +0200 [thread overview]
Message-ID: <18756925.NSB5aJaqC9@wuerfel> (raw)
In-Reply-To: <08c7bf360dfb7620591c0e0de6e047fffb0a5546.1461228081.git.viresh.kumar@linaro.org>
On Thursday 21 April 2016 14:13:48 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: Shawn Guo <shawnguo@kernel.org>
> Cc: Sascha Hauer <kernel@pengutronix.de>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> ---
> arch/arm/mach-imx/imx27-dt.c | 4 ----
> arch/arm/mach-imx/mach-imx51.c | 3 ---
> arch/arm/mach-imx/mach-imx53.c | 2 --
> arch/arm/mach-imx/mach-imx7d.c | 6 ------
> drivers/cpufreq/cpufreq-dt-platdev.c | 5 +++++
> 5 files changed, 5 insertions(+), 15 deletions(-)
>
> diff --git a/arch/arm/mach-imx/imx27-dt.c b/arch/arm/mach-imx/imx27-dt.c
> index bd42d1bd10af..90c62bf01f9e 100644
> --- a/arch/arm/mach-imx/imx27-dt.c
> +++ b/arch/arm/mach-imx/imx27-dt.c
> @@ -20,11 +20,7 @@
>
> static void __init imx27_dt_init(void)
> {
> - struct platform_device_info devinfo = { .name = "cpufreq-dt", };
> -
> of_platform_populate(NULL, of_default_bus_match_table, NULL, NULL);
> -
> - platform_device_register_full(&devinfo);
> }
>
Please remove the entire function now, a NULL .init_machine machine
callback pointer has the same effect as the remaining line.
The rest of the patch is fine.
Arnd
next prev parent reply other threads:[~2016-04-21 9:47 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 [this message]
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 ` [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=18756925.NSB5aJaqC9@wuerfel \
--to=arnd@arndb.de \
--cc=arnd.bergmann@linaro.org \
--cc=kernel@pengutronix.de \
--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=shawnguo@kernel.org \
--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