From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] replace bzero with memset
Date: Tue, 1 Dec 2015 19:24:09 -0800 [thread overview]
Message-ID: <1449026652-7320-1-git-send-email-stephen@networkplumber.org> (raw)
The DPDK is mostly consistent about using the POSIX standard
memset instead of bzero; but there seem to be some leftover BSD
hold outs.
Stephen Hemminger (3):
test-pmd: use memset not bzero
xen-virt: use memset not bzero
qat: use memset instead of bzero
app/test-pmd/testpmd.c | 4 ++--
drivers/net/xenvirt/rte_eth_xenvirt.c | 3 ++-
examples/dpdk_qat/crypto.c | 8 ++++----
3 files changed, 8 insertions(+), 7 deletions(-)
--
2.1.4
next reply other threads:[~2015-12-02 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 3:24 Stephen Hemminger [this message]
2015-12-02 3:24 ` [dpdk-dev] [PATCH 1/3] test-pmd: use memset not bzero Stephen Hemminger
2015-12-02 3:24 ` [dpdk-dev] [PATCH 2/3] xen-virt: " Stephen Hemminger
2015-12-02 3:24 ` [dpdk-dev] [PATCH 3/3] qat: use memset instead of bzero Stephen Hemminger
2015-12-02 8:28 ` [dpdk-dev] [PATCH 0/3] replace bzero with memset De Lara Guarch, Pablo
2015-12-06 22:51 ` Thomas Monjalon
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=1449026652-7320-1-git-send-email-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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).