From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: Update MTD infrastructure to support 64bit device size
Date: Mon, 22 Jun 2009 22:04:05 +0200 [thread overview]
Message-ID: <4A3FE3B5.7060608@googlemail.com> (raw)
In-Reply-To: <4A3FE10D.50601@freescale.com>
Scott Wood wrote:
> Dirk Behme wrote:
>> What I still miss: If this warning indicates that something *is*
>> wrong, why not run MAKEALL and enable it in config for all boards that
>> show this warning? What's the advantage of having all maintainers
>> sending patches for their boards?
>
> 1. That requires having all toolchains installed, and
Hmm? In nand_util.c we have
#if !defined(CONFIG_SYS_64BIT_VSPRINTF)
#warning Please define CONFIG_SYS_64BIT_VSPRINTF for correct output!
#endif
and in Makefile we have
ifdef CONFIG_CMD_NAND
ifndef CONFIG_NAND_LEGACY
...
COBJS-y += nand_util.o
endif
So I would assume that this warning appears for all boards having
CONFIG_CMD_NAND enabled and no CONFIG_NAND_LEGACY and no
CONFIG_SYS_64BIT_VSPRINTF? Independent of tool chain?
> 2. That does nothing to prevent future boards from being added that are
> missing the dependency.
Ok, for future boards this warning is fine. But I talk about all the
existing boards.
Best regards
Dirk
next prev parent reply other threads:[~2009-06-22 20:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 14:03 [U-Boot] [PATCH] mtd: Update MTD infrastructure to support 64bit device size Stefan Roese
2009-05-11 16:27 ` Mike Frysinger
2009-05-11 16:38 ` Stefan Roese
2009-05-11 16:57 ` Mike Frysinger
2009-05-11 20:06 ` Scott Wood
2009-05-11 17:59 ` Wolfgang Denk
2009-05-12 4:39 ` Stefan Roese
2009-05-12 5:11 ` Mike Frysinger
2009-05-12 8:14 ` Wolfgang Denk
2009-05-12 8:26 ` Stefan Roese
2009-06-03 21:49 ` Wolfgang Denk
2009-06-20 5:33 ` Dirk Behme
2009-06-20 8:52 ` Jean-Christophe PLAGNIOL-VILLARD
2009-06-20 17:45 ` Dirk Behme
2009-06-22 12:01 ` Stefan Roese
2009-06-22 18:10 ` Dirk Behme
2009-06-22 18:21 ` Stefan Roese
2009-06-28 5:47 ` Dirk Behme
2009-06-29 14:35 ` Stefan Roese
2009-06-22 12:55 ` Stefan Roese
2009-06-22 18:12 ` Dirk Behme
2009-06-22 18:25 ` Stefan Roese
2009-06-22 18:38 ` Dirk Behme
2009-06-22 18:50 ` Scott Wood
2009-06-22 19:26 ` Stefan Roese
2009-06-22 19:49 ` Dirk Behme
2009-06-22 19:52 ` Scott Wood
2009-06-22 20:04 ` Dirk Behme [this message]
2009-06-22 20:08 ` Scott Wood
2009-06-22 20:15 ` Dirk Behme
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=4A3FE3B5.7060608@googlemail.com \
--to=dirk.behme@googlemail.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