linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Kamat <sachin.kamat@linaro.org>
To: linux-pm@vger.kernel.org
Cc: cpufreq@vger.kernel.org, rjw@rjwysocki.net,
	viresh.kumar@linaro.org, sachin.kamat@linaro.org,
	Lukasz Majewski <l.majewski@samsung.com>
Subject: [PATCH 1/1] cpufreq: exynos: Fix compilation warnings
Date: Tue, 19 Nov 2013 09:53:39 +0530	[thread overview]
Message-ID: <1384835019-3251-1-git-send-email-sachin.kamat@linaro.org> (raw)

Commit a403797bbd81 ("cpufreq: exynos: Convert exynos-cpufreq
to platform driver") forgot to change the function prototype.
Change it now to fix the following compilation warnings:

drivers/cpufreq/exynos-cpufreq.c:292:18: warning: incorrect type in initializer
(different argument counts)
drivers/cpufreq/exynos-cpufreq.c:292:18:    expected int ( *probe )( ... )
drivers/cpufreq/exynos-cpufreq.c:292:18:    got int ( static [toplevel]
*<noident> )( ... )
  CC      drivers/cpufreq/exynos-cpufreq.o
drivers/cpufreq/exynos-cpufreq.c:292:2: warning: initialization from
incompatible pointer type [enabled by default]
  .probe = exynos_cpufreq_init,
  ^
drivers/cpufreq/exynos-cpufreq.c:292:2: warning: (near initialization for
‘exynos_cpufreq_platdrv.probe’) [enabled by default]
  LD      drivers/cpufreq/built-in.o

WARNING: drivers/cpufreq/built-in.o(.data+0x644): Section mismatch in reference
from the variable exynos_cpufreq_platdrv to the function
.init.text:exynos_cpufreq_init()

Signed-off-by: Sachin Kamat <sachin.kamat@linaro.org>
Cc: Lukasz Majewski <l.majewski@samsung.com>
---
 drivers/cpufreq/exynos-cpufreq.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufreq/exynos-cpufreq.c
index a2f57d4101fc..e238c46efaac 100644
--- a/drivers/cpufreq/exynos-cpufreq.c
+++ b/drivers/cpufreq/exynos-cpufreq.c
@@ -233,7 +233,7 @@ static struct cpufreq_driver exynos_driver = {
 #endif
 };
 
-static int __init exynos_cpufreq_init(void)
+static int exynos_cpufreq_init(struct platform_device *pdev)
 {
 	int ret = -EINVAL;
 
-- 
1.7.9.5


             reply	other threads:[~2013-11-19  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  4:23 Sachin Kamat [this message]
2013-11-19  4:59 ` [PATCH 1/1] cpufreq: exynos: Fix compilation warnings Viresh Kumar
2013-11-19  5:07   ` Sachin Kamat
2013-11-27  7:03     ` Lukasz Majewski

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=1384835019-3251-1-git-send-email-sachin.kamat@linaro.org \
    --to=sachin.kamat@linaro.org \
    --cc=cpufreq@vger.kernel.org \
    --cc=l.majewski@samsung.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=viresh.kumar@linaro.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).