From: Tigran Aivazian <tigran@aivazian.fsnet.co.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] microcode: Fix mc_cpu_notifier section warning
Date: Mon, 18 Dec 2006 10:04:39 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0612180954380.3848@ws.homenet> (raw)
In-Reply-To: <20061217173602.abaf4b69.khali@linux-fr.org>
Hi Jean,
Ok, your patch is correct, although I assume you realize that it does
nothing --- both the function and the data it operates on are inside
CONFIG_HOTPLUG_CPU and checking include/linux/init.h I see that
__cpuinitdata is nothing in this case. E.g. msr_class_cpu_notifier in the
msr driver isn't declared __cpuinitdata...
But to tidy up one should add __cpuinitdata as you suggest (to guard for
the case if these two slip out of CONFIG_HOTPLUG_CPU, although they are
meaningless if cpu hotplug support is not configured in).
Kind regards
Tigran
On Sun, 17 Dec 2006, Jean Delvare wrote:
> Structure mc_cpu_notifier references a __cpuinit function, but
> isn't declared __cpuinitdata itself:
>
> WARNING: arch/i386/kernel/microcode.o - Section mismatch: reference
> to .init.text: from .data after 'mc_cpu_notifier' (at offset 0x118)
>
> Signed-off-by: Jean Delvare <khali@linux-fr.org>
> ---
> arch/i386/kernel/microcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-2.6.20-rc1.orig/arch/i386/kernel/microcode.c 2006-12-15 09:05:20.000000000 +0100
> +++ linux-2.6.20-rc1/arch/i386/kernel/microcode.c 2006-12-17 15:23:40.000000000 +0100
> @@ -722,7 +722,7 @@
> return NOTIFY_OK;
> }
>
> -static struct notifier_block mc_cpu_notifier = {
> +static struct notifier_block __cpuinitdata mc_cpu_notifier = {
> .notifier_call = mc_cpu_callback,
> };
>
>
>
> --
> Jean Delvare
>
next prev parent reply other threads:[~2006-12-18 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-17 16:36 Jean Delvare
2006-12-18 10:04 ` Tigran Aivazian [this message]
2006-12-19 7:33 ` Jean Delvare
2006-12-19 9:10 ` Tigran Aivazian
2006-12-21 0:49 ` Andrew Morton
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=Pine.LNX.4.61.0612180954380.3848@ws.homenet \
--to=tigran@aivazian.fsnet.co.uk \
--cc=khali@linux-fr.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
all inboxes | Powered by JetHome®