From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>, Ingo Molnar <mingo@elte.hu>
Subject: [PATCH 2/7] x86: fix section mismatch warning - reserve_region_with_split
Date: Sun, 12 Oct 2008 11:44:07 +0200 [thread overview]
Message-ID: <1223804652-11033-1-git-send-email-marcin.slusarz@gmail.com> (raw)
In-Reply-To: <1223804330-10881-1-git-send-email-marcin.slusarz@gmail.com>
reserve_region_with_split calls __init function (__reserve_region_with_split)
and is called only from __init function (e820_reserve_resources_late),
so mark it __init
WARNING: vmlinux.o(.text+0x30299): Section mismatch in reference from the function reserve_region_with_split() to the function .init.text:__reserve_region_with_split()
The function reserve_region_with_split() references
the function __init __reserve_region_with_split().
This is often because reserve_region_with_split lacks a __init
annotation or the annotation of __reserve_region_with_split is wrong.
Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>
---
kernel/resource.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/resource.c b/kernel/resource.c
index 414d6fc..914cea6 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -575,7 +575,7 @@ static void __init __reserve_region_with_split(struct resource *root,
}
-void reserve_region_with_split(struct resource *root,
+void __init reserve_region_with_split(struct resource *root,
resource_size_t start, resource_size_t end,
const char *name)
{
--
1.5.6.4
next prev parent reply other threads:[~2008-10-12 9:44 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 ` [PATCH 1/7] x86, xsave: fix section mismatch warning - setup_xstate_init Marcin Slusarz
2008-10-12 9:44 ` Marcin Slusarz [this message]
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=1223804652-11033-1-git-send-email-marcin.slusarz@gmail.com \
--to=marcin.slusarz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yhlu.kernel@gmail.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