From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>, dev@dpdk.org
Cc: linuxarm@huawei.com, xavier_huwei@163.com, xavier.huwei@tom.com,
forest.zhouchang@huawei.com
Subject: Re: [dpdk-dev] [PATCH v2 0/4] some fixes for hns3 PMD driver
Date: Fri, 25 Oct 2019 16:07:29 +0100 [thread overview]
Message-ID: <b538b68c-9bd2-a170-78f7-bdf0794ce2ab@intel.com> (raw)
In-Reply-To: <1572007025-43391-1-git-send-email-xavier.huwei@huawei.com>
On 10/25/2019 1:37 PM, Wei Hu (Xavier) wrote:
> This series adds some fixes for hns3 ethernet pmd driver.
>
> v1 -> v2:
> 1. Address some comments from Ferruh Yigit as belows:
> https://inbox.dpdk.org/dev/31868759-1900-2aad-4e38-0ae8fe52647a@intel.com
> https://inbox.dpdk.org/dev/e5d5bd99-663d-5661-dfda-312c762b2887@intel.com
> https://inbox.dpdk.org/dev/b4a32414-b941-c820-1706-f8ad41175764@intel.com
>
> Chunsong Feng (1):
> net/hns3: fix FLR reset failure
>
> Hao Chen (1):
> net/hns3: fix the statistics problems about Tx/Rx functions
>
> Hongbo Zheng (1):
> net/hns3: fix the return value when firmware timeout
>
> Wei Hu (Xavier) (1):
> net/hns3: fix lack of Rx RSS hash in ol flags
Series applied to dpdk-next-net/master, thanks.
next prev parent reply other threads:[~2019-10-25 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 12:37 Wei Hu (Xavier)
2019-10-25 12:37 ` [dpdk-dev] [PATCH v2 1/4] net/hns3: fix the statistics problems about Tx/Rx functions Wei Hu (Xavier)
2019-10-25 12:37 ` [dpdk-dev] [PATCH v2 2/4] net/hns3: fix lack of Rx RSS hash in ol flags Wei Hu (Xavier)
2019-10-25 12:37 ` [dpdk-dev] [PATCH v2 3/4] net/hns3: fix the return value when firmware timeout Wei Hu (Xavier)
2019-10-25 12:37 ` [dpdk-dev] [PATCH v2 4/4] net/hns3: fix FLR reset failure Wei Hu (Xavier)
2019-10-25 15:07 ` Ferruh Yigit [this message]
2019-10-26 1:03 ` [dpdk-dev] [PATCH v2 0/4] some fixes for hns3 PMD driver Wei Hu (Xavier)
2019-10-26 1:56 ` Wei Hu (Xavier)
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=b538b68c-9bd2-a170-78f7-bdf0794ce2ab@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=forest.zhouchang@huawei.com \
--cc=linuxarm@huawei.com \
--cc=xavier.huwei@huawei.com \
--cc=xavier.huwei@tom.com \
--cc=xavier_huwei@163.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).