From: Mike Frysinger <vapier@gentoo.org>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net,
Markos Chandras <Markos.Chandras@imgtec.com>
Subject: Re: [LTP] [PATCH 05/21] syscalls: Cast st_nlink variables to proper integers
Date: Tue, 3 Jan 2012 18:34:44 -0500 [thread overview]
Message-ID: <201201031834.45745.vapier@gentoo.org> (raw)
In-Reply-To: <CAGH67wSrnkWdC8vYubfur6p2-Vs03F6LKvnZumtb-ZW-dWLy8g@mail.gmail.com>
[-- Attachment #1.1: Type: Text/Plain, Size: 272 bytes --]
On Tuesday 03 January 2012 17:19:25 Garrett Cooper wrote:
> The 'solution' for the issues with
> format strings and long integers is generally cast to [u]intmax_t,
> then use %zd or %zu.
eek, almost ;)
ssize_t -> %zd
size_t -> %zu
intmax_t -> %jd
uintmax_t -> %ju
-mike
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 355 bytes --]
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
[-- Attachment #3: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2012-01-03 23:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 10:42 [LTP] [PATCH 05/21] syscalls: Cast st_nlink variables to proper integers Markos Chandras
2012-01-03 19:35 ` Garrett Cooper
2012-01-03 20:37 ` Mike Frysinger
2012-01-03 20:51 ` Garrett Cooper
2012-01-03 20:57 ` Mike Frysinger
2012-01-03 22:19 ` Garrett Cooper
2012-01-03 23:34 ` Mike Frysinger [this message]
2012-01-03 23:52 ` Garrett Cooper
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=201201031834.45745.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Markos.Chandras@imgtec.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=yanegomi@gmail.com \
/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