From: Mathieu Rondonneau <mathieu.rondonneau@gmail.com>
To: mathieu.rondonneau@gmail.com, rostedt <rostedt@goodmis.org>,
fweisbec <fweisbec@gmail.com>, mingo <mingo@redhat.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>,
davem@davemloft.net
Subject: [PATH][RESUBMITTING] fixing harmless warning about __cpuinit in processor_idle.c
Date: Thu, 8 Oct 2009 13:27:53 -0700 [thread overview]
Message-ID: <b92cb9ab0910081327u6fb1eex84537620c4aa421b@mail.gmail.com> (raw)
fix harmless warnings that causes compiler warning:
WARNING: drivers/acpi/built-in.o(.text+0x21945): Section mismatch in
reference from the function acpi_processor_add() to the function
.cpuinit.text:acpi_processor_power_init()
The function acpi_processor_add() references
the function __cpuinit acpi_processor_power_init().
change files: driver/acpi/processor_idle.c
Signed-off-by: Mathieu Rondonneau <mathieu.rondonneau@gmail.com>
---
diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
index bbd066e..166457a 100644
--- a/drivers/acpi/processor_idle.c
+++ b/drivers/acpi/processor_idle.c
@@ -105,7 +105,7 @@ static int set_max_cstate(const struct dmi_system_id *id)
/* Actually this shouldn't be __cpuinitdata, would be better to fix the
callers to only run once -AK */
-static struct dmi_system_id __cpuinitdata processor_power_dmi_table[] = {
+static struct dmi_system_id processor_power_dmi_table[] = {
{ set_max_cstate, "Clevo 5600D", {
DMI_MATCH(DMI_BIOS_VENDOR,"Phoenix Technologies LTD"),
DMI_MATCH(DMI_BIOS_VERSION,"SHE845M0.86C.0013.D.0302131307")},
@@ -1158,7 +1158,7 @@ int acpi_processor_cst_has_changed(struct
acpi_processor *pr)
return ret;
}
-int __cpuinit acpi_processor_power_init(struct acpi_processor *pr,
+int acpi_processor_power_init(struct acpi_processor *pr,
struct acpi_device *device)
{
acpi_status status = 0;
reply other threads:[~2009-10-08 20:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=b92cb9ab0910081327u6fb1eex84537620c4aa421b@mail.gmail.com \
--to=mathieu.rondonneau@gmail.com \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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
all inboxes | Powered by JetHome®