From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/5] cpufreq: exynos: remove Exynos4x12 specific cpufreq driver support
Date: Sat, 1 Aug 2015 16:20:13 +0530 [thread overview]
Message-ID: <20150801105013.GG899@linux> (raw)
In-Reply-To: <1438368557-2352-5-git-send-email-b.zolnierkie@samsung.com>
Cc'ing Rafael, please keep him in loop for such patches and better use
get_maintainers to get the cc list automatically.
On 31-07-15, 20:49, Bartlomiej Zolnierkiewicz wrote:
> Exynos4x12 based platforms have switched over to use generic
> cpufreq driver for cpufreq functionality. So the Exynos
> specific cpufreq support for these platforms can be removed.
>
> Also once Exynos4x12 based platforms support have been removed
> the shared exynos-cpufreq driver is no longer needed and can
> be deleted.
>
> Based on the earlier work by Thomas Abraham.
>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Thomas Abraham <thomas.ab@samsung.com>
> Reviewed-by: Javier Martinez Canillas <javier@osg.samsung.com>
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
> Signed-off-by: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
> ---
> drivers/cpufreq/Kconfig.arm | 38 ------
> drivers/cpufreq/Makefile | 2 -
> drivers/cpufreq/exynos-cpufreq.c | 236 -----------------------------------
> drivers/cpufreq/exynos-cpufreq.h | 72 -----------
> drivers/cpufreq/exynos4x12-cpufreq.c | 236 -----------------------------------
> 5 files changed, 584 deletions(-)
> delete mode 100644 drivers/cpufreq/exynos-cpufreq.c
> delete mode 100644 drivers/cpufreq/exynos-cpufreq.h
> delete mode 100644 drivers/cpufreq/exynos4x12-cpufreq.c
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2015-08-01 10:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 18:49 [PATCH v3 0/5] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Bartlomiej Zolnierkiewicz
2015-07-31 18:49 ` [PATCH v3 1/5] clk: samsung: exynos4x12: add cpu clock configuration data and instantiate cpu clock Bartlomiej Zolnierkiewicz
2015-07-31 18:49 ` [PATCH v3 2/5] ARM: dts: Exynos4x12: add CPU OPP and regulator supply property Bartlomiej Zolnierkiewicz
2015-08-01 10:48 ` Viresh Kumar
2015-07-31 18:49 ` [PATCH v3 3/5] ARM: Exynos: switch to using generic cpufreq driver for Exynos4x12 Bartlomiej Zolnierkiewicz
2015-08-01 7:43 ` Krzysztof Kozlowski
2015-08-03 10:31 ` Bartlomiej Zolnierkiewicz
2015-08-01 11:17 ` Viresh Kumar
2015-08-03 10:17 ` Bartlomiej Zolnierkiewicz
2015-08-03 10:29 ` Viresh Kumar
2015-08-03 10:36 ` Bartlomiej Zolnierkiewicz
2015-08-03 10:40 ` Viresh Kumar
2015-08-03 10:47 ` Bartlomiej Zolnierkiewicz
2015-08-03 11:15 ` Krzysztof Kozlowski
2015-08-03 13:55 ` Bartlomiej Zolnierkiewicz
2015-08-03 15:50 ` Viresh Kumar
2015-08-03 15:57 ` Bartlomiej Zolnierkiewicz
2015-08-04 0:43 ` Krzysztof Kozlowski
2015-07-31 18:49 ` [PATCH v3 4/5] cpufreq: exynos: remove Exynos4x12 specific cpufreq driver support Bartlomiej Zolnierkiewicz
2015-08-01 10:50 ` Viresh Kumar [this message]
2015-07-31 18:49 ` [PATCH v3 5/5] cpufreq: remove no longer needed CPU_FREQ_BOOST_SW config option Bartlomiej Zolnierkiewicz
2015-08-01 11:15 ` Viresh Kumar
2015-08-03 17:12 ` Pandruvada, Srinivas
2015-08-04 1:09 ` Rafael J. Wysocki
2015-08-03 20:55 ` [PATCH v3 0/5] cpufreq: use generic cpufreq drivers for Exynos4x12 platform Tobias Jakobi
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=20150801105013.GG899@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).