From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-next@vger.kernel.org,
Suzuki Poulose <suzuki@in.ibm.com>,
Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org
Subject: linux-next: build warnings after merge of the 4xx tree
Date: Wed, 21 Dec 2011 11:13:49 +1100 [thread overview]
Message-ID: <20111221111349.c9d73384a0a2c89cd211239e@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 831 bytes --]
Hi Josh,
After merging the 4xx tree, today's linux-next build (powerpc ppc64_defconfig)
produced these warnings:
WARN: Uncompressed kernel (size 0xe32858) overlaps the address of the wrapper()
WARN: Fixing the link_address of wrapper to (0xf00000)
WARN: Uncompressed kernel (size 0xd6c9e8) overlaps the address of the wrapper(0x400000)
WARN: Fixing the link_address of wrapper to (0xe00000)
Introduced by commit c55aef0e5bc6 ("powerpc/boot: Change the load address
for the wrapper to fit the kernel"). Maybe "WARN" is not the best
prefix for this. To me it implies that something may go wrong and there
is something to be fixed ... If this is purely informational, then maybe
"INFO" would be better.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-12-21 0:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 0:13 Stephen Rothwell [this message]
2011-12-21 1:11 ` linux-next: build warnings after merge of the 4xx tree Josh Boyer
2011-12-21 7:20 ` [PATCH] [boot] Change the WARN to INFO for boot wrapper overlap message Suzuki K. Poulose
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=20111221111349.c9d73384a0a2c89cd211239e@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=suzuki@in.ibm.com \
/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).