public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: [PATCH 1/7] x86, xsave: fix section mismatch warning - setup_xstate_init
Date: Sun, 12 Oct 2008 11:38:44 +0200	[thread overview]
Message-ID: <1223804330-10881-2-git-send-email-marcin.slusarz@gmail.com> (raw)
In-Reply-To: <1223804330-10881-1-git-send-email-marcin.slusarz@gmail.com>

setup_xstate_init calls __init function (alloc_bootmem) and is called only
from __init function (xsave_cntxt_init), so mark it static __init

WARNING: vmlinux.o(.text+0x8f7b): Section mismatch in reference from the function setup_xstate_init() to the function .init.text:__alloc_bootmem()
The function setup_xstate_init() references
the function __init __alloc_bootmem().
This is often because setup_xstate_init lacks a __init
annotation or the annotation of __alloc_bootmem is wrong.

Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>
---
 arch/x86/kernel/xsave.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/arch/x86/kernel/xsave.c b/arch/x86/kernel/xsave.c
index 07713d6..ed5274a 100644
--- a/arch/x86/kernel/xsave.c
+++ b/arch/x86/kernel/xsave.c
@@ -272,7 +272,7 @@ void __cpuinit xsave_init(void)
 /*
  * setup the xstate image representing the init state
  */
-void setup_xstate_init(void)
+static void __init setup_xstate_init(void)
 {
 	init_xstate_buf = alloc_bootmem(xstate_size);
 	init_xstate_buf->i387.mxcsr = MXCSR_DEFAULT;
-- 
1.5.6.4


  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 [PATCH 0/7] post x86 merge section mismatch fixes Marcin Slusarz
2008-10-12  9:38 ` Marcin Slusarz [this message]
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-2-git-send-email-marcin.slusarz@gmail.com \
    --to=marcin.slusarz@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    /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