[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+5PVA7NhzxwxR5WGDmUQ432NehNnzRT+y05wve+FBXHyGaiwA@mail.gmail.com>
Date: Tue, 20 Dec 2011 20:11:17 -0500
From: Josh Boyer <jwboyer@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Suzuki Poulose <suzuki@...ibm.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org
Subject: Re: linux-next: build warnings after merge of the 4xx tree
On Tue, Dec 20, 2011 at 7:13 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 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.
INFO indeed would be better. I'll try and whip up a patch tomorrow
unless Suzie beats me to it.
Sorry about that. I saw the WARN during my testing, but the commit
log explicitly mentioned it an brainwashed me into thinking it was OK.
I blame holiday-itis.
josh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists