From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: xiaoyun.li@intel.com, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] app/testpmd: fix Tx/Rx descriptor query error log
Date: Tue, 30 Mar 2021 15:29:18 +0100 [thread overview]
Message-ID: <40f4b2cb-8c24-077b-0144-3729b06f2d97@intel.com> (raw)
In-Reply-To: <1617000403-13647-1-git-send-email-humin29@huawei.com>
On 3/29/2021 7:46 AM, Min Hu (Connor) wrote:
> From: Hongbo Zheng <zhenghongbo3@huawei.com>
>
> This patch adds more err info for Tx/Rx descriptor query command.
>
> Fixes: fae9aa717d6c ("app/testpmd: support checking descriptor status")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hongbo Zheng <zhenghongbo3@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
Off the topic.
This is the patch 90000 in patchwork!
Thanks to everyone who contributed!
https://patches.dpdk.org/api/1.2/patches/90000/
The historical numbers from DPDK patchwork:
90000 - March 29, 2021 (172 days) [ 5 months and 21 days / 24 weeks and 4 days ]
80000 - Oct. 8, 2020 (153 days)
70000 - May 8, 2020 (224 days)
60000 - Sept. 27, 2019 (248 days)
50000 - Jan. 22, 2019 (253 days)
40000 - May 14, 2018 (217 days)
30000 - Oct. 9, 2017 (258 days)
20000 - Jan. 25, 2017 (372 days)
10000 - Jan. 20, 2016 (645 days)
00001 - April 16, 2014
Another 10K of patches faster than rough average ~250 days, assuming v20.11 LTS
workload contributed to this stat but not investigated deeply.
Thanks again to all contributors.
prev parent reply other threads:[~2021-03-30 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 7:34 [dpdk-dev] [PATCH] " Min Hu (Connor)
2021-03-29 5:49 ` Li, Xiaoyun
2021-03-29 6:47 ` Min Hu (Connor)
2021-03-29 6:46 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-03-29 7:07 ` Li, Xiaoyun
2021-03-30 14:35 ` Ferruh Yigit
2021-03-30 14:29 ` Ferruh Yigit [this message]
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=40f4b2cb-8c24-077b-0144-3729b06f2d97@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=humin29@huawei.com \
--cc=techboard@dpdk.org \
--cc=xiaoyun.li@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).