From: Stefano Babic <sbabic@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 1/3] Define uintptr_t as long int to simplify printf() format strings
Date: Tue, 22 Nov 2011 09:49:27 +0100 [thread overview]
Message-ID: <4ECB6217.4090900@denx.de> (raw)
In-Reply-To: <1320424957-32385-1-git-send-email-sjg@chromium.org>
On 04/11/2011 17:42, Simon Glass wrote:
> If uintptr_t can be either an unsigned int or an unsigned long int, it is
> tricky to use it in a printf() format string. This changes it to
> unsigned long int consistently. This should do the right thing on both
> 32-bit and 64-bit architectures.
>
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
Applied to u-boot-staging, sbabic at denx.de, thanks.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
prev parent reply other threads:[~2011-11-22 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-04 16:42 [U-Boot] [PATCH v3 1/3] Define uintptr_t as long int to simplify printf() format strings Simon Glass
2011-11-04 16:42 ` [U-Boot] [PATCH v3 2/3] Fix warnings in cmd_nvedit.c Simon Glass
2011-11-22 8:50 ` Stefano Babic
2011-11-04 16:42 ` [U-Boot] [PATCH v3 3/3] sandbox: Fix warnings in hashtable.c Simon Glass
2011-11-04 20:07 ` [U-Boot] [PATCH v3 1/3] Define uintptr_t as long int to simplify printf() format strings Mike Frysinger
2011-11-22 8:49 ` Stefano Babic [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=4ECB6217.4090900@denx.de \
--to=sbabic@denx.de \
--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.