From: Adrian Bunk <bunk@kernel.org>
To: Chris Clayton <chris2553@googlemail.com>, davej@codemonkey.org.uk
Cc: linux-kernel@vger.kernel.org, cpufreq@lists.linux.org.uk
Subject: [2.6 patch] drivers/cpufreq/cpufreq_stats.c section fix
Date: Sun, 2 Dec 2007 01:43:04 +0100 [thread overview]
Message-ID: <20071202004304.GG15974@stusta.de> (raw)
In-Reply-To: <200711291419.49261.chris2553@googlemail.com>
cpufreq_stats_free_table() mustn't be __cpuexit since it's called by the
__cpuinit cpufreq_stat_cpu_callback().
This patch fixes the following section mismatch reported by
Chris Clayton:
<-- snip -->
...
WARNING: vmlinux.o(.init.text+0x143dd): Section mismatch: reference to .exit.text:cpufreq_stats_free_table (between 'cpufreq_stat_cpu_callback' and 'cpufreq_stats_init')
...
<-- snip -->
Signed-off-by: Adrian Bunk <bunk@kernel.org>
---
b845706570b48f091f855c33cdb9979d7e83a424
diff --git a/drivers/cpufreq/cpufreq_stats.c b/drivers/cpufreq/cpufreq_stats.c
index 8a45d0f..1b8312b 100644
--- a/drivers/cpufreq/cpufreq_stats.c
+++ b/drivers/cpufreq/cpufreq_stats.c
@@ -164,7 +164,7 @@ freq_table_get_index(struct cpufreq_stats *stat, unsigned int freq)
return -1;
}
-static void __cpuexit cpufreq_stats_free_table(unsigned int cpu)
+static void cpufreq_stats_free_table(unsigned int cpu)
{
struct cpufreq_stats *stat = cpufreq_stats_table[cpu];
struct cpufreq_policy *policy = cpufreq_cpu_get(cpu);
prev parent reply other threads:[~2007-12-02 0:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 14:19 2.6.24-rc3-git4 build warnings Chris Clayton
2007-11-29 18:00 ` Adrian Bunk
2007-11-30 10:41 ` Chris Clayton
2007-12-01 19:36 ` Adrian Bunk
2007-12-01 19:49 ` Chris Clayton
2007-12-01 20:01 ` Adrian Bunk
2007-12-02 0:42 ` [2.6 patch] x86 intel_cacheinfo.c section fix Adrian Bunk
2007-12-04 12:56 ` Ingo Molnar
2007-12-02 0:43 ` Adrian Bunk [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=20071202004304.GG15974@stusta.de \
--to=bunk@kernel.org \
--cc=chris2553@googlemail.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.