From: Zhiyong Yang <zhiyong.yang@intel.com>
To: dev@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: [dpdk-dev] [PATCH 0/5] remove void pointer explicit cast
Date: Mon, 26 Feb 2018 16:10:58 +0800 [thread overview]
Message-ID: <20180226081103.64154-1-zhiyong.yang@intel.com> (raw)
The patch series cleanup void pointer explicit cast related to
struct rte_flow_item fields in librte_flow_classify and make
code more readable.
Zhiyong Yang (5):
flow_classify: remove void pointer cast
net/ixgbe: remove void pointer cast
net/e1000: remove void pointer cast
net/bnxt: remove void pointer cast
net/sfc: remove void pointer cast
drivers/net/bnxt/bnxt_filter.c | 44 ++++-----
drivers/net/e1000/igb_flow.c | 27 +++---
drivers/net/ixgbe/ixgbe_flow.c | 106 +++++++++------------
drivers/net/sfc/sfc_flow.c | 8 +-
lib/librte_flow_classify/rte_flow_classify.c | 4 +-
lib/librte_flow_classify/rte_flow_classify_parse.c | 24 ++---
6 files changed, 93 insertions(+), 120 deletions(-)
--
2.13.3
next reply other threads:[~2018-02-26 8:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 8:10 Zhiyong Yang [this message]
2018-02-26 8:10 ` [dpdk-dev] [PATCH 1/5] flow_classify: remove void pointer cast Zhiyong Yang
2018-03-14 11:02 ` Iremonger, Bernard
2018-02-26 8:11 ` [dpdk-dev] [PATCH 2/5] net/ixgbe: " Zhiyong Yang
2018-02-26 8:11 ` [dpdk-dev] [PATCH 3/5] net/e1000: " Zhiyong Yang
2018-02-26 8:11 ` [dpdk-dev] [PATCH 4/5] net/bnxt: " Zhiyong Yang
2018-02-26 8:11 ` [dpdk-dev] [PATCH 5/5] net/sfc: " Zhiyong Yang
2018-02-26 11:03 ` Andrew Rybchenko
2018-02-27 13:45 ` [dpdk-dev] [PATCH 0/5] remove void pointer explicit cast Ferruh Yigit
2018-03-06 18:57 ` Ferruh Yigit
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=20180226081103.64154-1-zhiyong.yang@intel.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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;
as well as URLs for NNTP newsgroup(s).