All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Chris Friesen" <cfriesen@nortel.com>
To: linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: section mismatch warnings in current git head for powerpc
Date: Thu, 22 May 2008 11:22:35 -0600	[thread overview]
Message-ID: <4835ABDB.8020901@nortel.com> (raw)

I got the following warnings when building current git head for powerpc 
64bit:


   LD      net/ipv4/built-in.o
   LD      drivers/scsi/built-in.o
   LD      net/built-in.o
   LD      drivers/built-in.o
   LD      vmlinux.o
   MODPOST vmlinux.o
WARNING: vmlinux.o(.text+0x73bc): Section mismatch in reference from the 
function .start_secondary_prolog() to the function 
.devinit.text:.start_secondary()
The function .start_secondary_prolog() references
the function __devinit .start_secondary().
This is often because .start_secondary_prolog lacks a __devinit
annotation or the annotation of .start_secondary is wrong.

WARNING: vmlinux.o(.text+0x260a8): Section mismatch in reference from 
the function .pci_dn_reconfig_notifier() to the function 
.devinit.text:.update_dn_pci_info()
The function .pci_dn_reconfig_notifier() references
the function __devinit .update_dn_pci_info().
This is often because .pci_dn_reconfig_notifier lacks a __devinit
annotation or the annotation of .update_dn_pci_info is wrong.


Is this anything to worry about?

Thanks,
Chris

             reply	other threads:[~2008-05-22 17:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-22 17:22 Chris Friesen [this message]
2008-05-22 17:50 ` section mismatch warnings in current git head for powerpc Bart Van Assche
2008-05-22 17:50   ` Bart Van Assche
2008-05-23  1:02 ` Michael Ellerman
2008-05-23  1:02   ` Michael Ellerman

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=4835ABDB.8020901@nortel.com \
    --to=cfriesen@nortel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.