From: Viresh Kumar <viresh.kumar@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH 23/47] cpufreq: remove cris specific drivers
Date: Thu, 15 Mar 2018 08:17:32 +0530 [thread overview]
Message-ID: <20180315024732.GI15832@vireshk-i7> (raw)
In-Reply-To: <20180314153603.3127932-24-arnd@arndb.de>
On 14-03-18, 16:35, Arnd Bergmann wrote:
> The cris architecture is getting removed, including the artpec3
> and etraxfs SoCs, so these cpufreq drivers are now unused.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> ---
> drivers/cpufreq/Makefile | 2 -
> drivers/cpufreq/cris-artpec3-cpufreq.c | 93 ----------------------------------
> drivers/cpufreq/cris-etraxfs-cpufreq.c | 92 ---------------------------------
> 3 files changed, 187 deletions(-)
> delete mode 100644 drivers/cpufreq/cris-artpec3-cpufreq.c
> delete mode 100644 drivers/cpufreq/cris-etraxfs-cpufreq.c
>
> diff --git a/drivers/cpufreq/Makefile b/drivers/cpufreq/Makefile
> index 2e4495cf9aa8..8d24ade3bd02 100644
> --- a/drivers/cpufreq/Makefile
> +++ b/drivers/cpufreq/Makefile
> @@ -102,8 +102,6 @@ obj-$(CONFIG_POWERNV_CPUFREQ) += powernv-cpufreq.o
> ##################################################################################
> # Other platform drivers
> obj-$(CONFIG_BMIPS_CPUFREQ) += bmips-cpufreq.o
> -obj-$(CONFIG_CRIS_MACH_ARTPEC3) += cris-artpec3-cpufreq.o
> -obj-$(CONFIG_ETRAXFS) += cris-etraxfs-cpufreq.o
> obj-$(CONFIG_IA64_ACPI_CPUFREQ) += ia64-acpi-cpufreq.o
> obj-$(CONFIG_LOONGSON2_CPUFREQ) += loongson2_cpufreq.o
> obj-$(CONFIG_LOONGSON1_CPUFREQ) += loongson1-cpufreq.o
> diff --git a/drivers/cpufreq/cris-artpec3-cpufreq.c b/drivers/cpufreq/cris-artpec3-cpufreq.c
> deleted file mode 100644
> index 455b4fb78cba..000000000000
> diff --git a/drivers/cpufreq/cris-etraxfs-cpufreq.c b/drivers/cpufreq/cris-etraxfs-cpufreq.c
> deleted file mode 100644
> index 4c4b5dd685e3..000000000000
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
next prev parent reply other threads:[~2018-03-15 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:35 [PATCH 00/47] arch-removal: device drivers Arnd Bergmann
2018-03-14 15:35 ` [PATCH 22/47] cpufreq: remove blackfin driver Arnd Bergmann
2018-03-15 2:47 ` Viresh Kumar
2018-03-14 15:35 ` [PATCH 23/47] cpufreq: remove cris specific drivers Arnd Bergmann
2018-03-15 2:47 ` Viresh Kumar [this message]
2018-03-15 12:19 ` Jesper Nilsson
2018-03-14 22:45 ` [PATCH 00/47] arch-removal: device drivers Rafael J. Wysocki
2018-03-15 5:32 ` Boris Brezillon
2018-03-15 9:09 ` 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=20180315024732.GI15832@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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