From: York Sun <yorksun@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] lib/fdtdec: Fix compiling warning for debug
Date: Thu, 16 Jul 2015 10:00:52 -0700 [thread overview]
Message-ID: <55A7E344.7000508@freescale.com> (raw)
In-Reply-To: <CAPnjgZ2GX4UMfb1y5t41M8pMt0GeGJwTOGciWvX-_jvcgcOihg@mail.gmail.com>
On 07/16/2015 09:40 AM, Simon Glass wrote:
> Hi,
>
> On 16 July 2015 at 01:01, Albert ARIBAUD <albert.u.boot@aribaud.net> wrote:
>> Hello York,
>>
>> On Wed, 15 Jul 2015 13:26:46 -0700, York Sun <yorksun@freescale.com>
>> wrote:
>>> fdt_addr_t and fdt_size_t can be either 64-bit or 32-bit, depending
>>> on the architecture. Change the type to phys_addr_t and phys_size_t.
>>
>> If the only reason for changing the type is to avoid warnings in
>> debug() then I don't think this is the right approach (see my message
>> re PRIu64).
>>
>> If, on the other hand, there is reason to believe the fdt_addr_t and
>> fdt_size_t are wrongly defined and should be typedef'd or ~define's as
>> phys_*_t, then the rationale for this should be exposed.
>>
>> Amicalement,
>> --
>> Albert.
>
> For LBA we do this in ide.h:
>
> #ifdef CONFIG_SYS_64BIT_LBA
> typedef uint64_t lbaint_t;
> #define LBAF "%llx"
> #define LBAFU "%llu"
> #else
> typedef ulong lbaint_t;
> #define LBAF "%lx"
> #define LBAFU "%lu"
> #endif
>
> How about something similar for this case? It would be nice to avoid
> promoting everything to 64-bit given that very few platforms are
> actually 64-bit.
>
Simon,
Do you think fdt_addr_t should be phys_addr_t? According to the comments you put
in file, "A typedef for a physical address". If yes, I can change the commit
message.
On the other hand, if we want to keep the current typedef, we can use Albert's
PRIu64 technique, we then don't have to define the format string.
York
next prev parent reply other threads:[~2015-07-16 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-15 20:26 [U-Boot] [RFC] lib/fdtdec: Fix compiling warning for debug York Sun
2015-07-16 7:01 ` Albert ARIBAUD
2015-07-16 16:40 ` Simon Glass
2015-07-16 17:00 ` York Sun [this message]
2015-07-16 17:10 ` Simon Glass
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=55A7E344.7000508@freescale.com \
--to=yorksun@freescale.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