From: Steve Heflin <sheflin@newagemicro.com>
To: linuxppc-embedded@ozlabs.org
Subject: 2.6.25-rc3 Sequoia build - section mismatch(es)
Date: Thu, 28 Feb 2008 18:21:38 -0500 [thread overview]
Message-ID: <20080228232115.6C911DDEC1@ozlabs.org> (raw)
Upon building the default Sequoia (AMCC-440EPx) configuration, the
MODPOST step warns about section mismatches:
WARNING: modpost: Found 5 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
After using the CONFIG_DEBUG_SECTION_MISMATCH option, the section
mismatches are cases in one of the following:
1) functions in the device initialization (.devinit)
calls routines which are contained in the .text section;
2) functions in the device init section calls routines in the
device exit section;
3) data structures in the .data section contain pointers to
functions in the .devinit section or .devexit section; (note that
these data structures are used during initialization)
My question is, will this cause the code to malfunction?
thanks,
Steve
next reply other threads:[~2008-02-28 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 23:21 Steve Heflin [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-24 10:17 Status of 5200B and 440 Kernel Support Albrecht Dreß
2008-02-24 13:38 ` Josh Boyer
2008-02-28 23:07 ` 2.6.25-rc3 Sequoia build - section mismatch(es) Steve Heflin
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=20080228232115.6C911DDEC1@ozlabs.org \
--to=sheflin@newagemicro.com \
--cc=linuxppc-embedded@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).