From: Wei Zhao <wei.zhao1@intel.com>
To: dev@dpdk.org
Cc: qi.z.zhang@intel.com
Subject: [dpdk-dev] [PATCH 0/2] add support for check descriptor status APIs
Date: Thu, 8 Feb 2018 16:36:28 +0800 [thread overview]
Message-ID: <20180208083630.103388-1-wei.zhao1@intel.com> (raw)
The patches set mainly finish following functions:
Igb VF and fm10k nic add support check descriptor status APIs.
wei zhao (2):
net/e1000: add support for check descriptor status APIs
net/fm10k: add support for check descriptor status APIs
drivers/net/e1000/igb_ethdev.c | 3 ++
drivers/net/fm10k/fm10k.h | 7 +++++
drivers/net/fm10k/fm10k_ethdev.c | 2 ++
drivers/net/fm10k/fm10k_rxtx.c | 65 ++++++++++++++++++++++++++++++++++++++++
4 files changed, 77 insertions(+)
--
2.9.3
next reply other threads:[~2018-02-08 8:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 8:36 Wei Zhao [this message]
2018-02-08 8:36 ` [dpdk-dev] [PATCH 1/2] net/e1000: " Wei Zhao
2018-06-20 8:52 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-06-27 8:37 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-29 1:52 ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-07-02 7:42 ` Zhao1, Wei
2018-07-02 13:03 ` Zhang, Qi Z
2018-07-02 13:12 ` Zhang, Qi Z
2018-02-08 8:36 ` [dpdk-dev] [PATCH 2/2] net/fm10k: " Wei Zhao
2018-06-20 8:44 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-06-22 7:53 ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-06-22 8:20 ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-06-27 8:10 ` Zhang, Qi Z
2018-06-27 8:18 ` Zhao1, Wei
2018-06-27 8:18 ` Zhang, Qi Z
2018-06-27 9:09 ` Zhao1, Wei
2018-06-27 8:24 ` [dpdk-dev] [PATCH v5] " Wei Zhao
2018-06-27 8:26 ` Wei Zhao
2018-06-29 1:48 ` [dpdk-dev] [PATCH v6] " Wei Zhao
2018-06-29 11:03 ` Ferruh Yigit
2018-07-02 1:46 ` Zhao1, Wei
2018-07-02 7:15 ` [dpdk-dev] [PATCH v7] " Zhao Wei
2018-07-02 13:07 ` Zhang, Qi Z
2018-07-02 13:11 ` Zhang, Qi Z
2018-06-27 12:49 ` [dpdk-dev] [PATCH v4] " Zhang, Qi Z
2018-06-29 1:22 ` Zhao1, Wei
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=20180208083630.103388-1-wei.zhao1@intel.com \
--to=wei.zhao1@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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).