From: Roger Quadros <ext-roger.quadros@nokia.com>
To: "Kucheria Amit (EXT-Atomide/Helsinki)"
<ext-amit.kucheria@nokia.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: OMAP3: RX51: build warning at rx51_t2scripts
Date: Wed, 01 Jul 2009 11:02:41 +0300 [thread overview]
Message-ID: <4A4B1821.20604@nokia.com> (raw)
Hi Amit,
I get the following warning while building Kevin's PM branch for RX-51.
The kernel boots to shell though.
I'm not sure whether it's harmless or not.
MODPOST vmlinux.o
WARNING: vmlinux.o(.data+0xb328): Section mismatch in reference from the
variable rx51_t2scripts_data to the (unknown reference) .init.data:(unknown)
The variable rx51_t2scripts_data references
the (unknown reference) __initdata (unknown)
If the reference is valid then annotate the
variable with __init* (see linux/init.h) or name the variable:
*driver, *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
next reply other threads:[~2009-07-01 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 8:02 Roger Quadros [this message]
2009-07-01 11:38 ` OMAP3: RX51: build warning at rx51_t2scripts Kucheria Amit
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=4A4B1821.20604@nokia.com \
--to=ext-roger.quadros@nokia.com \
--cc=ext-amit.kucheria@nokia.com \
--cc=linux-omap@vger.kernel.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