From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Lijun Ou <oulijun@huawei.com>, thomas@monjalon.net
Cc: dev@dpdk.org, linuxarm@openeuler.org
Subject: Re: [dpdk-dev] [PATCH 00/14] Misc updates for hns3
Date: Thu, 28 Jan 2021 23:58:43 +0000 [thread overview]
Message-ID: <2112b2de-c179-d3c5-bdb8-c931353e188f@intel.com> (raw)
In-Reply-To: <1611310732-51975-1-git-send-email-oulijun@huawei.com>
On 1/22/2021 10:18 AM, Lijun Ou wrote:
> This series add a new feature LSC event report and
> two bugfixes as well as some cleanup patches.
>
> Chengchang Tang (2):
> net/hns3: reconstruct the Rx interrupt map
> net/hns3: fix interrupt resources in Rx interrupt mode
>
> Chengwen Feng (1):
> net/hns3: support LSC event report
>
> Huisong Li (2):
> net/hns3: encapsulate dfx stats in Rx/Tx datapatch
> net/hns3: move queue stats to xstats
>
> Lijun Ou (9):
> net/hns3: use array instead of switch-case
> net/hns3: move judgment conditions to separated functions
> net/hns3: extract common judgments for all FDIR type
> net/hns3: refactor reset event report function
> net/hns3: fix memory leak with secondary process exit
> net/hns3: rename RSS functions
> net/hns3: adjust some comments
> net/hns3: remove unnecessary parentheses
> net/hns3: use %d instead of %u for enum variable
LSC interrupt patch (14/14) may need to be updated, and since it has no
dependency in the set it is not merged, can be sent separately later.
Except 14/14,
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-01-28 23:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 10:18 Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 01/14] net/hns3: encapsulate dfx stats in Rx/Tx datapatch Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 02/14] net/hns3: move queue stats to xstats Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 03/14] net/hns3: use array instead of switch-case Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 04/14] net/hns3: move judgment conditions to separated functions Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 05/14] net/hns3: reconstruct the Rx interrupt map Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 06/14] net/hns3: extract common judgments for all FDIR type Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 07/14] net/hns3: refactor reset event report function Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 08/14] net/hns3: fix memory leak with secondary process exit Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 09/14] net/hns3: fix interrupt resources in Rx interrupt mode Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 10/14] net/hns3: rename RSS functions Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 11/14] net/hns3: adjust some comments Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 12/14] net/hns3: remove unnecessary parentheses Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 13/14] net/hns3: use %d instead of %u for enum variable Lijun Ou
2021-01-22 10:18 ` [dpdk-dev] [PATCH 14/14] net/hns3: support LSC event report Lijun Ou
2021-01-28 23:41 ` Ferruh Yigit
2021-01-29 1:49 ` oulijun
2021-02-02 12:06 ` Ferruh Yigit
2021-02-02 12:12 ` Ferruh Yigit
2021-01-28 23:58 ` 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=2112b2de-c179-d3c5-bdb8-c931353e188f@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=linuxarm@openeuler.org \
--cc=oulijun@huawei.com \
--cc=thomas@monjalon.net \
/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).