From: Viresh Kumar <viresh.kumar@linaro.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, Dave Gerlach <d-gerlach@ti.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
linux-pm@vger.kernel.org
Subject: Re: [PATCH] cpufreq: make ti-cpufreq explicitly non-modular
Date: Tue, 14 Feb 2017 09:19:14 +0530 [thread overview]
Message-ID: <20170214034914.GD3537@vireshk-i7> (raw)
In-Reply-To: <20170214004502.9181-1-paul.gortmaker@windriver.com>
On 13-02-17, 19:45, Paul Gortmaker wrote:
> The Kconfig currently controlling compilation of this code is:
>
> drivers/cpufreq/Kconfig.arm:config ARM_TI_CPUFREQ
> drivers/cpufreq/Kconfig.arm: bool "Texas Instruments CPUFreq support"
>
> ...meaning that it currently is not being built as a module by anyone.
>
> Lets remove the couple traces of modular infrastructure use, so that
> when reading the driver there is no doubt it is builtin-only.
>
> Since module_init translates to device_initcall in the non-modular
> case, the init ordering remains unchanged with this commit.
>
> We also delete the MODULE_LICENSE tag etc. since all that information
> is already contained at the top of the file in the comments.
>
> Cc: Viresh Kumar <viresh.kumar@linaro.org>
> Cc: Dave Gerlach <d-gerlach@ti.com>
> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> Cc: linux-pm@vger.kernel.org
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> ---
> drivers/cpufreq/ti-cpufreq.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/cpufreq/ti-cpufreq.c b/drivers/cpufreq/ti-cpufreq.c
> index 7ff7ae3c3911..a7b5658c0460 100644
> --- a/drivers/cpufreq/ti-cpufreq.c
> +++ b/drivers/cpufreq/ti-cpufreq.c
> @@ -17,7 +17,7 @@
> #include <linux/cpu.h>
> #include <linux/io.h>
> #include <linux/mfd/syscon.h>
> -#include <linux/module.h>
> +#include <linux/init.h>
> #include <linux/of.h>
> #include <linux/of_platform.h>
> #include <linux/pm_opp.h>
> @@ -265,8 +265,4 @@ static int ti_cpufreq_init(void)
>
> return ret;
> }
> -module_init(ti_cpufreq_init);
> -
> -MODULE_DESCRIPTION("TI CPUFreq/OPP hw-supported driver");
> -MODULE_AUTHOR("Dave Gerlach <d-gerlach@ti.com>");
> -MODULE_LICENSE("GPL v2");
> +device_initcall(ti_cpufreq_init);
Acked-by: Viresh Kumar <viresh.kumar@linaro.org>
--
viresh
prev parent reply other threads:[~2017-02-14 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 0:45 [PATCH] cpufreq: make ti-cpufreq explicitly non-modular Paul Gortmaker
2017-02-14 3:49 ` Viresh Kumar [this message]
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=20170214034914.GD3537@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=d-gerlach@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=rafael.j.wysocki@intel.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).