From: Rakib Mullick <rakib.mullick@gmail.com>
To: linux-acpi@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Len Brown <lenb@kernel.org>
Subject: [PATCH] acpi: Annote acpi_processor_add with __cpuinit.
Date: Fri, 2 Oct 2009 11:15:24 +0600 [thread overview]
Message-ID: <b9df5fa10910012215u6f6cbb8w3a8e667aec43dab4@mail.gmail.com> (raw)
Annote acpi_processor_add with cpuinit since it calls a cpuinit function
acpi_processor_power_init and fixes a section mismatch warning.
We were warned by the following warning:
LD drivers/acpi/processor.o
WARNING: drivers/acpi/processor.o(.text+0x1829): 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().
This is often because acpi_processor_add lacks a __cpuinit
annotation or the annotation of acpi_processor_power_init is wrong.
-------
Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
--- linus/drivers/acpi/processor_core.c 2009-09-28 12:04:54.000000000 +0600
+++ rakib/drivers/acpi/processor_core.c 2009-09-29 23:21:13.000000000 +0600
@@ -770,7 +770,7 @@ static struct notifier_block acpi_cpu_no
.notifier_call = acpi_cpu_soft_notify,
};
-static int acpi_processor_add(struct acpi_device *device)
+static int __cpuinit acpi_processor_add(struct acpi_device *device)
{
struct acpi_processor *pr = NULL;
int result = 0;
next reply other threads:[~2009-10-02 5:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-02 5:15 Rakib Mullick [this message]
2009-11-05 21:50 ` [PATCH] acpi: Annote acpi_processor_add with __cpuinit Len Brown
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=b9df5fa10910012215u6f6cbb8w3a8e667aec43dab4@mail.gmail.com \
--to=rakib.mullick@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox