From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] ARM: U-boot and 2 GiB of ram with get_ram_size only being long
Date: Tue, 15 Oct 2013 09:12:41 +0200 [thread overview]
Message-ID: <20131015091241.48901e5c@lilith> (raw)
In-Reply-To: <52521F5B.4090002@schinagl.nl>
Hi Oliver,
On Mon, 07 Oct 2013 04:41:31 +0200, Oliver Schinagl
<oliver+list@schinagl.nl> wrote:
> Hey all,
>
> Having not received any feed back at all, I went ahead and did the
> changes anyway. Everything seems to run and work fine for sunxi and
> prints proper sizes.
>
> For the other boards, I tried to run a MAKEALL but there where so many
> random other warnings I can't say for 100% certainty there where no
> mistakes that crept in.
There cannot possibly be a single warning if you're working from an
official U-Boot repo, as warnings are considered failures and thus no
patch reaches u-boot/master if it causes a warning. Thus, any warning
stems from the change you're introducing, and they are probably due to
a few common causes.
Can you provide a rough analysis/classification of the warnings?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2013-10-15 7:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 21:15 [U-Boot] [RFC] ARM: U-boot and 2 GiB of ram with get_ram_size only being long Oliver Schinagl
2013-10-07 2:41 ` Oliver Schinagl
2013-10-15 7:12 ` Albert ARIBAUD [this message]
2013-10-15 17:57 ` Scott Wood
2013-10-17 6:27 ` Albert ARIBAUD
2013-10-18 0:04 ` Oliver Schinagl
2013-10-18 16:43 ` Scott Wood
2013-10-18 20:26 ` Wolfgang Denk
2013-10-18 21:04 ` Scott Wood
2013-10-18 21:53 ` Wolfgang Denk
2013-10-18 23:11 ` Oliver Schinagl
2013-10-18 23:07 ` Oliver Schinagl
2013-10-18 23:25 ` Scott Wood
2013-10-18 23:25 ` Scott Wood
2013-10-19 9:21 ` Oliver Schinagl
2013-10-19 9:07 ` Oliver Schinagl
2013-10-19 18:25 ` Tom Rini
2013-10-21 19:44 ` Wolfgang Denk
2014-03-24 10:14 ` Olliver Schinagl
2013-10-15 18:01 ` Scott Wood
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=20131015091241.48901e5c@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.