From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>
Subject: [PATCH 0/7] post x86 merge section mismatch fixes
Date: Sun, 12 Oct 2008 11:38:43 +0200 [thread overview]
Message-ID: <1223804330-10881-1-git-send-email-marcin.slusarz@gmail.com> (raw)
[PATCH 1/7] x86, xsave: fix section mismatch warning - setup_xstate_init
[PATCH 2/7] x86: fix section mismatch warning - reserve_region_with_split
[PATCH 3/7] x86: fix section mismatch warning - apic_flat
[PATCH 4/7] x86: fix section mismatch warning - apic_physflat
[PATCH 5/7] x86: fix section mismatch warning - apic_x2apic_uv_x
[PATCH 6/7] x86: fix section mismatch warning - apic_x2apic_cluster
[PATCH 7/7] x86: fix section mismatch warning - apic_x2apic_phys
arch/x86/kernel/genapic_flat_64.c | 4 ++--
arch/x86/kernel/genx2apic_cluster.c | 2 +-
arch/x86/kernel/genx2apic_phys.c | 2 +-
arch/x86/kernel/genx2apic_uv_x.c | 2 +-
arch/x86/kernel/xsave.c | 2 +-
kernel/resource.c | 2 +-
6 files changed, 7 insertions(+), 7 deletions(-)
One warning left:
WARNING: vmlinux.o(.cpuinit.text+0x4ad): Section mismatch in reference from the function fpu_init() to the function .init.text:init_thread_xstate()
The function __cpuinit fpu_init() references
a function __init init_thread_xstate().
If init_thread_xstate is only used by fpu_init then
annotate init_thread_xstate with a matching annotation.
x86_64 cpu_init() (marked __cpu_init) calls fpu_init() (marked __cpu_init)
and fpu_init calls init_thread_xstate (which is __init) if smp_processor_id() == 0.
So it's probably OK, but it should be fixed properly (without ugly __ref)
Marcin
next reply other threads:[~2008-10-12 9:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-12 9:38 Marcin Slusarz [this message]
2008-10-12 9:38 ` [PATCH 1/7] x86, xsave: fix section mismatch warning - setup_xstate_init Marcin Slusarz
2008-10-12 9:44 ` [PATCH 2/7] x86: fix section mismatch warning - reserve_region_with_split Marcin Slusarz
2008-10-12 9:44 ` [PATCH 3/7] x86: fix section mismatch warning - apic_flat Marcin Slusarz
2008-10-12 9:44 ` [PATCH 4/7] x86: fix section mismatch warning - apic_physflat Marcin Slusarz
2008-10-12 9:44 ` [PATCH 5/7] x86: fix section mismatch warning - apic_x2apic_uv_x Marcin Slusarz
2008-10-12 9:44 ` [PATCH 6/7] x86: fix section mismatch warning - apic_x2apic_cluster Marcin Slusarz
2008-10-12 9:46 ` [PATCH 7/7] x86: fix section mismatch warning - apic_x2apic_phys Marcin Slusarz
2008-10-22 15:37 ` [PATCH 0/7] post x86 merge section mismatch fixes Ingo Molnar
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=1223804330-10881-1-git-send-email-marcin.slusarz@gmail.com \
--to=marcin.slusarz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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