From: "Wei Hu (Xavier)" <xavier.huwei@huawei.com>
To: <ferruh.yigit@intel.com>
Cc: "Wei Hu (Xavier)" <xavier.huwei@tom.com>, <dev@dpdk.org>,
Jeremy Plsek <jplsek@iol.unh.edu>, <aconole@redhat.com>,
Ali Alnubani <alialnu@mellanox.com>,
"forest.zhouchang@huawei.com" <forest.zhouchang@huawei.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] updates for hns3 ethernet pmd driver
Date: Thu, 10 Oct 2019 11:28:12 +0800 [thread overview]
Message-ID: <bb1df2d2-0020-e07d-fca1-7ff5ec39ae4a@huawei.com> (raw)
In-Reply-To: <20191009141653.39364-1-xavier.huwei@tom.com>
Hi, Ferruh Yigit
The page in patches.dpdk.org indicates that CI checking against this
series failed, the page as follows:
http://mails.dpdk.org/archives/test-report/2019-October/101655.html
Just like the previous failure of patch CI checking, this series based
on dpdk-next-net repo but CI checking based on dpdk repo.
Thanks.
Regards
Xavier
On 2019/10/9 22:16, Wei Hu (Xavier) wrote:
> This series adds some updates for hns3 ethernet pmd driver.
>
> The No.1 patch modifies the statistics information for sending
> and receiving packets.
> The No.2 patch changes the return value of firmware processing
> timeout from -EBADE to -ETIME.
> The No.3 patch adds commands between driver and firmware.
> The No.4 patch restores bus_master_en and msix_enable during
> PF FLR reset.
>
> Chunsong Feng (1):
> net/hns3: restores bus_master_en and msix_enable during PF FLR reset
>
> Hao Chen (1):
> net/hns3: modify the statistics for sending and receiving messages
>
> Hongbo Zheng (1):
> net/hns3: change the return value of firmware processing timeout from
> -EBADE to -ETIME
>
> humin (1):
> net/hns3: Renew command and desc structure
>
> drivers/net/hns3/hns3_cmd.c | 17 +---
> drivers/net/hns3/hns3_cmd.h | 9 +-
> drivers/net/hns3/hns3_ethdev.c | 5 ++
> drivers/net/hns3/hns3_ethdev_vf.c | 135 +++++++++++++++++++++++++++++-
> drivers/net/hns3/hns3_intr.c | 5 +-
> drivers/net/hns3/hns3_rxtx.c | 11 +--
> drivers/net/hns3/hns3_rxtx.h | 3 -
> drivers/net/hns3/hns3_stats.c | 84 +++++--------------
> 8 files changed, 168 insertions(+), 101 deletions(-)
>
next prev parent reply other threads:[~2019-10-10 3:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:16 Wei Hu (Xavier)
2019-10-09 14:16 ` [dpdk-dev] [PATCH 1/4] net/hns3: modify the statistics for sending and receiving messages Wei Hu (Xavier)
2019-10-15 8:45 ` Ferruh Yigit
2019-10-18 8:23 ` Wei Hu (Xavier)
2019-10-09 14:16 ` [dpdk-dev] [PATCH 2/4] net/hns3: change the return value of firmware processing timeout from -EBADE to -ETIME Wei Hu (Xavier)
2019-10-09 14:16 ` [dpdk-dev] [PATCH 3/4] net/hns3: Renew command and desc structure Wei Hu (Xavier)
2019-10-15 8:45 ` Ferruh Yigit
2019-10-25 12:34 ` Wei Hu (Xavier)
2019-10-09 14:16 ` [dpdk-dev] [PATCH 4/4] net/hns3: restores bus_master_en and msix_enable during PF FLR reset Wei Hu (Xavier)
2019-10-10 3:28 ` Wei Hu (Xavier) [this message]
2019-10-15 8:46 ` [dpdk-dev] [PATCH 0/4] updates for hns3 ethernet pmd driver Ferruh Yigit
2019-10-18 8:24 ` 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=bb1df2d2-0020-e07d-fca1-7ff5ec39ae4a@huawei.com \
--to=xavier.huwei@huawei.com \
--cc=aconole@redhat.com \
--cc=alialnu@mellanox.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=forest.zhouchang@huawei.com \
--cc=jplsek@iol.unh.edu \
--cc=xavier.huwei@tom.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).