From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
rakib.mullick@gmail.com, akpm@linux-foundation.org,
tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86: Fix false positive section mismatch warnings in the apic code
Date: Sun, 19 Apr 2009 11:47:08 +0200 [thread overview]
Message-ID: <49EAF31C.8020108@gmail.com> (raw)
In-Reply-To: <tip-aa57a15ad17d284e62fbd24cf7e0eb628b2cb3f7@git.kernel.org>
tip-bot for Rakib Mullick pisze:
> Commit-ID: aa57a15ad17d284e62fbd24cf7e0eb628b2cb3f7
> Gitweb: http://git.kernel.org/tip/aa57a15ad17d284e62fbd24cf7e0eb628b2cb3f7
> Author: Rakib Mullick <rakib.mullick@gmail.com>
> AuthorDate: Sun, 19 Apr 2009 08:41:17 +0600
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Sun, 19 Apr 2009 11:28:18 +0200
>
> x86: Fix false positive section mismatch warnings in the apic code
>
> find_unisys_acpi_oem_table() and unmap_unisys_acpi_oem_table() are non
> init functions, but these functions calls some init functions. But we
> need these functions as non-init functions.
Why? This warning seems to be valid.
>
> So annotate them via __ref.
>
> The following false positive warnings are fixed via this:
>
> WARNING: vmlinux.o(.text+0x16250): Section mismatch in reference from
> the function find_unisys_acpi_oem_table() to the function
> .init.text:early_acpi_os_unmap_memory()
> The function find_unisys_acpi_oem_table() references
> the function __init early_acpi_os_unmap_memory().
> This is often because find_unisys_acpi_oem_table lacks a __init
> annotation or the annotation of early_acpi_os_unmap_memory is wrong.
>
> WARNING: vmlinux.o(.text+0x16269): Section mismatch in reference from
> the function find_unisys_acpi_oem_table() to the function
> .init.text:early_acpi_os_unmap_memory()
> The function find_unisys_acpi_oem_table() references
> the function __init early_acpi_os_unmap_memory().
> This is often because find_unisys_acpi_oem_table lacks a __init
> annotation or the annotation of early_acpi_os_unmap_memory is wrong.
>
> WARNING: vmlinux.o(.text+0x16279): Section mismatch in reference from
> the function find_unisys_acpi_oem_table() to the function
> .init.text:__acpi_map_table()
> The function find_unisys_acpi_oem_table() references
> the function __init __acpi_map_table().
> This is often because find_unisys_acpi_oem_table lacks a __init
> annotation or the annotation of __acpi_map_table is wrong.
>
> WARNING: vmlinux.o(.text+0x16297): Section mismatch in reference from
> the function unmap_unisys_acpi_oem_table() to the function
> .init.text:__acpi_unmap_table()
> The function unmap_unisys_acpi_oem_table() references
> the function __init __acpi_unmap_table().
> This is often because unmap_unisys_acpi_oem_table lacks a __init
> annotation or the annotation of __acpi_unmap_table is wrong.
>
> [ Impact: annotate away section mismatch warnings ]
>
> Signed-off-by: Rakib Mullick <rakib.mullick@gmail.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> LKML-Reference: <b9df5fa10904181941u4a73fc97i80dfa90a50b8daf5@mail.gmail.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>
>
> ---
> arch/x86/kernel/apic/es7000_32.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kernel/apic/es7000_32.c b/arch/x86/kernel/apic/es7000_32.c
> index 1c11b81..96c150c 100644
> --- a/arch/x86/kernel/apic/es7000_32.c
> +++ b/arch/x86/kernel/apic/es7000_32.c
> @@ -254,7 +254,7 @@ static int parse_unisys_oem(char *oemptr)
> }
>
> #ifdef CONFIG_ACPI
> -static int find_unisys_acpi_oem_table(unsigned long *oem_addr)
> +static int __ref find_unisys_acpi_oem_table(unsigned long *oem_addr)
> {
> struct acpi_table_header *header = NULL;
> struct es7000_oem_table *table;
> @@ -285,7 +285,7 @@ static int find_unisys_acpi_oem_table(unsigned long *oem_addr)
> return 0;
> }
>
> -static void unmap_unisys_acpi_oem_table(unsigned long oem_addr)
> +static void __ref unmap_unisys_acpi_oem_table(unsigned long oem_addr)
> {
> if (!oem_addr)
> return;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2009-04-19 9:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 2:41 [PATCH] x86: Fix section mismatches in apic Rakib Mullick
2009-04-19 9:30 ` [tip:x86/urgent] x86: Fix false positive section mismatch warnings in the apic code tip-bot for Rakib Mullick
2009-04-19 9:47 ` Marcin Slusarz [this message]
2009-04-19 9:57 ` Ingo Molnar
2009-04-19 10:19 ` Marcin Slusarz
2009-04-19 13:56 ` Ingo Molnar
2009-04-19 11:16 ` Sam Ravnborg
2009-04-20 4:00 ` Rakib Mullick
2009-05-01 11:46 ` Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2009-05-09 9:35 [PATCH] x86: Fix false positive section mismatch in apic Rakib Mullick
2009-05-10 7:30 ` [tip:x86/urgent] x86: Fix false positive section mismatch warnings in the apic code tip-bot for Sam Ravnborg
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=49EAF31C.8020108@gmail.com \
--to=marcin.slusarz@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rakib.mullick@gmail.com \
--cc=tglx@linutronix.de \
/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