From: David Miller <davem@davemloft.net>
To: rmk+lkml@arm.linux.org.uk
Cc: cw@f00f.org, linux-kernel@vger.kernel.org, sam@ravnborg.org
Subject: Re: (hacky) [PATCH] silence MODPOST section mismatch warnings
Date: Thu, 10 May 2007 14:01:38 -0700 (PDT) [thread overview]
Message-ID: <20070510.140138.133012852.davem@davemloft.net> (raw)
In-Reply-To: <20070510204037.GE29713@flint.arm.linux.org.uk>
From: Russell King <rmk+lkml@arm.linux.org.uk>
Date: Thu, 10 May 2007 21:40:38 +0100
> On Thu, May 10, 2007 at 01:34:18PM -0700, Chris Wedgwood wrote:
> > MODPOST seems to be spewing bogus warnings. It's not clear how best
> > to fix it so perhaps we should silence it for now?
>
> I agree. Example bogus warning:
>
> WARNING: arch/arm/mach-iop32x/built-in.o - Section mismatch:
> reference to .init.text: from .data between 'iq80321_timer'
> (at offset 0x428) and 'iq80321_serial_device'
>
> c04088fc d iq80321_timer
> c0408950 d iq80321_serial_device
>
> It's completely unclear what is referencing what, what the two named
> symbols mean, and even what "at offset" relates to.
>
> What I can say is that iq80321_timer doesn't reference iq80321_serial_device
> nor vice versa, and iq80321_timer is far smaller than 0x428 bytes.
The range of symbols is just provided to handle inaccuracies
in mid-function and mid-object references, it actually helps.
In this particular case iq80321_timer, which is not init-data,
is referencing iq80321_timer_init() which is init.text
If this is legitimate (which I believe this case is, the init function
method can be init but the offset one is not), add an exception case
like we already have for console drivers et al. to modpost.c and this
warning will go away.
next prev parent reply other threads:[~2007-05-10 21:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 20:34 Chris Wedgwood
2007-05-10 20:40 ` Russell King
2007-05-10 21:01 ` David Miller [this message]
2007-05-10 21:14 ` Sam Ravnborg
2007-05-10 20:51 ` David Miller
2007-05-10 20:54 ` Russell King
2007-05-10 21:01 ` Sam Ravnborg
2007-05-11 6:28 ` Satyam Sharma
2007-05-10 21:07 ` David Miller
2007-05-10 21:23 ` Russell King
2007-05-10 21:59 ` Russell King
2007-05-10 22:03 ` [PATCH] Make modpost section warnings clearer Russell King
2007-05-10 22:08 ` David Miller
2007-05-10 22:16 ` (hacky) [PATCH] silence MODPOST section mismatch warnings Sam Ravnborg
2007-05-10 22:18 ` Russell King
2007-05-11 4:12 ` Sam Ravnborg
2007-05-11 18:54 ` Sam Ravnborg
2007-05-11 18:57 ` Russell King
2007-05-10 21:19 ` 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=20070510.140138.133012852.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®