From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/2] use %z for formatting
Date: Wed, 04 Apr 2018 12:41:08 +0200 [thread overview]
Message-ID: <6844497.rET6ehq5B7@xps> (raw)
In-Reply-To: <20180215222550.31128-1-stephen@networkplumber.org>
15/02/2018 23:25, Stephen Hemminger:
> Better to use %z and avoid any 32 bit platform woes;
> and not cast unnecessarily
>
> Stephen Hemminger (2):
> pci: use %z to format size_t
> eal: use %zu to format size_t
>
> lib/librte_eal/linuxapp/eal/eal_memory.c | 8 ++++----
> lib/librte_pci/rte_pci.c | 11 ++++++-----
> 2 files changed, 10 insertions(+), 9 deletions(-)
Applied, thanks
prev parent reply other threads:[~2018-04-04 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 22:25 Stephen Hemminger
2018-02-15 22:25 ` [dpdk-dev] [PATCH 1/2] pci: use %z to format size_t Stephen Hemminger
2018-02-15 22:25 ` [dpdk-dev] [PATCH 2/2] eal: use %zu " Stephen Hemminger
2018-04-04 10:41 ` Thomas Monjalon [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=6844497.rET6ehq5B7@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).