From: Daniel Kurtz <djkurtz@chromium.org>
Cc: Yidi Lin <yidi.lin@mediatek.com>,
Nicolas Boichat <drinkcat@chromium.org>,
Daniel Kurtz <djkurtz@chromium.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Viresh Kumar <viresh.kumar@linaro.org>,
"open list:CPU FREQUENCY DRIVERS" <linux-pm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: [PATCH 1/2] cpufreq: mt8173: Mark mt8173_cpufreq_driver_init as __init
Date: Thu, 2 Mar 2017 19:03:44 +0800 [thread overview]
Message-ID: <20170302110345.184924-1-djkurtz@chromium.org> (raw)
This function is only called once at boot by device_initcall(), so mark
it as __init.
Signed-off-by: Daniel Kurtz <djkurtz@chromium.org>
---
drivers/cpufreq/mt8173-cpufreq.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/mt8173-cpufreq.c b/drivers/cpufreq/mt8173-cpufreq.c
index ab25b1235a5e..72bc1192bd30 100644
--- a/drivers/cpufreq/mt8173-cpufreq.c
+++ b/drivers/cpufreq/mt8173-cpufreq.c
@@ -573,7 +573,7 @@ static struct platform_driver mt8173_cpufreq_platdrv = {
.probe = mt8173_cpufreq_probe,
};
-static int mt8173_cpufreq_driver_init(void)
+static int __init mt8173_cpufreq_driver_init(void)
{
struct platform_device *pdev;
int err;
--
2.12.0.rc1.440.g5b76565f74-goog
next reply other threads:[~2017-03-02 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 11:03 Daniel Kurtz [this message]
[not found] ` <20170302110345.184924-1-djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-02 11:03 ` [PATCH 2/2 v2] cpufreq: mediatek: Add support for MT8176 and MT817x Daniel Kurtz
[not found] ` <20170302110345.184924-2-djkurtz-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2017-03-02 11:07 ` Viresh Kumar
2017-03-02 11:06 ` [PATCH 1/2] cpufreq: mt8173: Mark mt8173_cpufreq_driver_init as __init Viresh Kumar
2017-03-02 11:30 ` Daniel Kurtz
-- strict thread matches above, loose matches on Subject: below --
2017-03-02 11:08 Daniel Kurtz
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=20170302110345.184924-1-djkurtz@chromium.org \
--to=djkurtz@chromium.org \
--cc=drinkcat@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.org \
--cc=yidi.lin@mediatek.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