From: "Suzuki K. Poulose" <suzuki@in.ibm.com>
To: Josh Boyer <jwboyer@gmail.com>, Stephen Rothwell<sfr@canb.auug.org.au>
Cc: linuxppc-dev@lists.ozlabs.org, paulus@samba.org,
linux-kernel@vger.kernel.org
Subject: [PATCH] [boot] Change the WARN to INFO for boot wrapper overlap message
Date: Wed, 21 Dec 2011 12:50:38 +0530 [thread overview]
Message-ID: <20111221072034.12043.62801.stgit@suzukikp.in.ibm.com> (raw)
In-Reply-To: <CA+5PVA7NhzxwxR5WGDmUQ432NehNnzRT+y05wve+FBXHyGaiwA@mail.gmail.com>
commit c55aef0e5bc6 ("powerpc/boot: Change the load address
for the wrapper to fit the kernel") introduced a WARNING to
inform the user that the uncompressed kernel would overlap
the boot uncompressing wrapper code. Change it to an INFO.
I initially thought, this would be a 'WARNING' for the those
boards, where the link_address should be fixed, so that the
user can take actions accordingly.
Changing the same to INFO.
Signed-off-by: Suzuki K. Poulose <suzuki@in.ibm.com>
---
arch/powerpc/boot/wrapper | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/powerpc/boot/wrapper b/arch/powerpc/boot/wrapper
index c8d6aaf..2b171cd 100755
--- a/arch/powerpc/boot/wrapper
+++ b/arch/powerpc/boot/wrapper
@@ -282,9 +282,9 @@ round_size=0x$(printf "%x" $round_size)
link_addr=$(printf "%d" $link_address)
if [ $link_addr -lt $strip_size ]; then
- echo "WARN: Uncompressed kernel (size 0x$(printf "%x\n" $strip_size))" \
+ echo "INFO: Uncompressed kernel (size 0x$(printf "%x\n" $strip_size))" \
"overlaps the address of the wrapper($link_address)"
- echo "WARN: Fixing the link_address of wrapper to ($round_size)"
+ echo "INFO: Fixing the link_address of wrapper to ($round_size)"
link_address=$round_size
fi
prev parent reply other threads:[~2011-12-21 7:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-21 0:13 linux-next: build warnings after merge of the 4xx tree Stephen Rothwell
2011-12-21 1:11 ` Josh Boyer
2011-12-21 7:20 ` Suzuki K. Poulose [this message]
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=20111221072034.12043.62801.stgit@suzukikp.in.ibm.com \
--to=suzuki@in.ibm.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
/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).