From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/3] get rid of unnecessary memset's
Date: Wed, 3 Jun 2015 14:13:09 -0700 [thread overview]
Message-ID: <1433365992-9173-1-git-send-email-stephen@networkplumber.org> (raw)
While looking at code is seems lots of drivers do not know the convention
that info_get and stats_get both clear the buffer for the caller.
Stephen Hemminger (3):
bonding: remove useless memset
ethdev: remove useless memset
null: remove unnecessary memset
drivers/net/bonding/rte_eth_bond_api.c | 1 -
drivers/net/bonding/rte_eth_bond_pmd.c | 4 ----
drivers/net/null/rte_eth_null.c | 1 -
lib/librte_ether/rte_ethdev.c | 1 -
4 files changed, 7 deletions(-)
--
2.1.4
next reply other threads:[~2015-06-03 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 21:13 Stephen Hemminger [this message]
2015-06-03 21:13 ` [dpdk-dev] [PATCH 1/3] bonding: remove useless memset Stephen Hemminger
2015-06-03 21:13 ` [dpdk-dev] [PATCH 2/3] ethdev: " Stephen Hemminger
2015-06-03 21:13 ` [dpdk-dev] [PATCH 3/3] null: remove unnecessary memset Stephen Hemminger
2015-06-04 8:47 ` [dpdk-dev] [PATCH 0/3] get rid of unnecessary memset's 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=1433365992-9173-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).