public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Section mismatch on current git head
Date: Sat, 23 Dec 2006 00:40:27 -0500	[thread overview]
Message-ID: <200612230040.28898.lenb@kernel.org> (raw)
In-Reply-To: <458BEAA9.6010503@m3y3r.de>


> WARNING: vmlinux - Section mismatch: reference to 
> .init.data:acpi_sci_flags from .text between 'acpi_sci_ioapic_setup' (at 
> offset 0xc010e020) and 'acpi_unmap_lsapic'
> WARNING: vmlinux - Section mismatch: reference to 
> .init.data:acpi_sci_flags from .text between 'acpi_sci_ioapic_setup' (at 
> offset 0xc010e04a) and 'acpi_unmap_lsapic'
> WARNING: vmlinux - Section mismatch: reference to 
> .init.text:mp_override_legacy_irq from .text between 
> 'acpi_sci_ioapic_setup' (at offset 0xc010e062) and 'acpi_unmap_lsapic'
> WARNING: vmlinux - Section mismatch: reference to 
> .init.data:acpi_sci_override_gsi from .text between 
> 'acpi_sci_ioapic_setup' (at offset 0xc010e068) and 'acpi_unmap_lsapic'

The acpi_sci_ioapic_setup ones should go away with the patch below, but do no harm in the mean-time.
cheers,
-Len

commit 0351a612f7a46995c28d4ef6189229b5d1dfc6c3
Author: Len Brown <len.brown@intel.com>
Date:   Thu Dec 21 01:29:59 2006 -0500

    ACPI: fix section mis-match build warning
    
    Dunno why this pops out in only in the allmodconfig build.
    Though the warning is accurate, all the callers of the flagged
    non __init function are __init, this is not a functional change.
    
    WARNING: vmlinux - Section mismatch: reference to .init.data:acpi_sci_flags from .text between 'acpi_sci_ioapic_setup' (at offset 0xc010f0a
    6) and 'acpi_gsi_to_irq'                                                                                                                   WARNING: vmlinux - Section mismatch: reference to .init.text:mp_override_legacy_irq from .text between 'acpi_sci_ioapic_setup' (at offset 0
    xc010f0de) and 'acpi_gsi_to_irq'                                                                                                           WARNING: vmlinux - Section mismatch: reference to .init.data:acpi_sci_override_gsi from .text between 'acpi_sci_ioapic_setup' (at offset 0x
    c010f0e4) and 'acpi_gsi_to_irq'
    
    Signed-off-by: Len Brown <len.brown@intel.com>

diff --git a/arch/i386/kernel/acpi/boot.c b/arch/i386/kernel/acpi/boot.c
index c8f96cf..45cffbf 100644
--- a/arch/i386/kernel/acpi/boot.c
+++ b/arch/i386/kernel/acpi/boot.c
@@ -333,7 +333,7 @@ acpi_parse_ioapic(acpi_table_entry_header * header, const unsigned long end)
 /*
  * Parse Interrupt Source Override for the ACPI SCI
  */
-static void acpi_sci_ioapic_setup(u32 gsi, u16 polarity, u16 trigger)
+static void __init acpi_sci_ioapic_setup(u32 gsi, u16 polarity, u16 trigger)
 {
 	if (trigger == 0)	/* compatible SCI trigger is level */
 		trigger = 3;


  parent reply	other threads:[~2006-12-23  5:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-22 14:24 Section mismatch on current git head Thomas Meyer
2006-12-22 17:47 ` Randy Dunlap
2007-01-03  6:00   ` Vivek Goyal
2006-12-23  5:40 ` Len Brown [this message]
2007-01-03  6:04   ` Vivek Goyal

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=200612230040.28898.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas@m3y3r.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