public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Commit 2108f4c4 causes a warning in 10 ARM boards
Date: Sat, 9 Nov 2013 07:18:23 -0500	[thread overview]
Message-ID: <527E280F.2090303@ti.com> (raw)
In-Reply-To: <20131109104954.59302d45@lilith>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/09/2013 04:49 AM, Albert ARIBAUD wrote:
> Hi Rob,
> 
> Commit 2108f4c4 ("config: consolidate CONFIG_SYS_HZ definition") causes
> the following boards:
> 
> 	omap730p2_cs3boot omap730p2_cs0boot scb9328 palmtc balloon3
> 	mini2440 zipitz2 palmld omap730p2 omap3_zoom2 mx1ads
> 
> to emit this warning:
> 
> 	time.c:12:2: warning: #warning "CONFIG_SYS_HZ must be 1000 and
> 	should not be defined by platforms" [-Wcpp]
> 
> Rob, can you look into it?
> 
> Tom: I am preparing a PR from ARM to u-boot; ARM build will obviously
> fail for these 10 boards unless a fix is applied to u-boot/master before
> I submit my PR.

This is intentional, as those boards have CONFIG_SYS_HZ wrong.  For the
PXA boards, Marek posted a patch that fixes them.  For omap730p2* I plan
to submit a patch to just yank them out.  For the others, we need to
find the board maintainer and get them to correct things, or pull them
as well.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJSfigPAAoJENk4IS6UOR1WHHcP/Rrk0EF1wuEm8/pQAc1foJQk
GWjVxXAZbz8UAKXLxroKUQlEzHyQZNc1kl3pBVF1txm9RaqAQsLNWu6Nro4lmPbE
DQVX0/0Elkdq2ZXpW2yw58VwS2IzFvfmw4cx0NkHsRTWLtZ4ZnkTEPoYB4GMY/dJ
LzuIw39OI1WhsbZDGvcbI+gT84ytymnahIFO48sd9+CA0UBJPbS8kjAJxKAIY1NK
Dnj3JBIp85pANE8BbNf4ZVLt/1AJqAdI8NE3AABhCsQQUFi6bHVqRCrlb2ln9pdG
IjvFTYCoQuYoo11XpPImfYEVYWSKLwwDctD6t2YV9qoZNz5KYqR5hNvlsgGIxR30
NHocVoOaAku0XgAXRpIzGqx+lV2dHSY0mgo8C/iY9cJsXe6CmLv8vFPs6K2L2AD8
TC/J0MVdx3x0fgVb1/dnt9ssLqcSGs3ohqnHopzuJlqau2lMJ8jRiwaGo8u9zoJQ
12ZdWkPeRo4varMUC7a5R0ZQ87v5MrXxZaupqvqRg7usndQnhnNmvUoJVwYPjVmB
DGqVBxQuOEkqHqoSJK3eCzo2E5+FBmumGgv53padIpTBhvVQuWZGjhhJRqakl1Yy
sHMi3hdfz99oFvaYm7rgDwxSAarm1jq37Q1VveUmf7Zc1YRVDxITb9F9P6IVApdU
la1SwdmHInTUzt5cjIWv
=/6uD
-----END PGP SIGNATURE-----

  reply	other threads:[~2013-11-09 12:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  9:49 [U-Boot] Commit 2108f4c4 causes a warning in 10 ARM boards Albert ARIBAUD
2013-11-09 12:18 ` Tom Rini [this message]
2013-11-09 12:55   ` Albert ARIBAUD

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=527E280F.2090303@ti.com \
    --to=trini@ti.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox