From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>,
arnd.bergmann@linaro.org, Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
kgene.kim@samsung.com, xf@rock-chips.com, heiko@sntech.de,
mmcclint@codeaurora.org, Viresh Kumar <viresh.kumar@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore
Date: Wed, 30 Mar 2016 13:45:27 +0530 [thread overview]
Message-ID: <abff8b995fce34ea80c68c5d11ccb8a525fb81fa.1459325515.git.viresh.kumar@linaro.org> (raw)
In-Reply-To: <cover.1459325515.git.viresh.kumar@linaro.org>
In-Reply-To: <cover.1459325515.git.viresh.kumar@linaro.org>
The driver is removed long back and we don't support this device
anymore. Stop adding it.
Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
---
arch/arm/mach-exynos/exynos.c | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/arch/arm/mach-exynos/exynos.c b/arch/arm/mach-exynos/exynos.c
index bbf51a46f772..4dfce1069406 100644
--- a/arch/arm/mach-exynos/exynos.c
+++ b/arch/arm/mach-exynos/exynos.c
@@ -232,12 +232,8 @@ static void __init exynos_cpufreq_init(void)
const struct of_device_id *match;
match = of_match_node(exynos_cpufreq_matches, root);
- if (!match) {
- platform_device_register_simple("exynos-cpufreq", -1, NULL, 0);
- return;
- }
-
- platform_device_register_simple(match->data, -1, NULL, 0);
+ if (match)
+ platform_device_register_simple(match->data, -1, NULL, 0);
}
static void __init exynos_dt_machine_init(void)
--
2.7.1.410.g6faf27b
next prev parent reply other threads:[~2016-03-30 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 8:15 [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-03-30 8:15 ` [PATCH V3 1/4] cpufreq: dt: Include types.h from cpufreq-dt.h Viresh Kumar
2016-03-30 8:15 ` [PATCH V3 2/4] cpufreq: dt: Add generic platform-device creation support Viresh Kumar
2016-04-13 19:46 ` Matthew McClintock
2016-03-30 8:15 ` Viresh Kumar [this message]
2016-03-30 8:30 ` [PATCH V3 3/4] ARM: exynos: exynos-cpufreq platform device isn't supported anymore Krzysztof Kozlowski
2016-03-30 8:15 ` [PATCH V3 4/4] cpufreq: exynos: Use generic platdev driver Viresh Kumar
2016-04-07 8:31 ` [PATCH V3 0/4] cpufreq: dt: Create platform device from generic code Viresh Kumar
2016-04-20 9:55 ` Viresh Kumar
2016-04-20 21:27 ` Mason
2016-04-20 22:31 ` Rafael J. Wysocki
2016-04-27 16:47 ` Mason
2016-04-27 16:57 ` Matthew McClintock
2016-04-28 2:27 ` 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=abff8b995fce34ea80c68c5d11ccb8a525fb81fa.1459325515.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=arnd.bergmann@linaro.org \
--cc=heiko@sntech.de \
--cc=k.kozlowski@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=kgene@kernel.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=linux-samsung-soc@vger.kernel.org \
--cc=mmcclint@codeaurora.org \
--cc=rjw@rjwysocki.net \
--cc=xf@rock-chips.com \
/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).