From: Jie Hai <haijie1@huawei.com>
To: <dev@dpdk.org>, <thomas@monjalon.net>, <ferruh.yigit@amd.com>
Cc: <lihuisong@huawei.com>, <fengchengwen@huawei.com>
Subject: Re: [PATCH 0/4] clean code for dmadev and hns3
Date: Sat, 12 Oct 2024 17:31:56 +0800 [thread overview]
Message-ID: <9ad96046-e503-6deb-3968-70455df63fcf@huawei.com> (raw)
In-Reply-To: <20240905064638.17980-1-haijie1@huawei.com>
On 2024/9/5 14:46, Jie Hai wrote:
The patch set will be seperate into 3 part and resend, please see
patch[1/4]
https://patches.dpdk.org/project/dpdk/patch/20241012091437.21382-1-haijie1@huawei.com/
patch[2/4]
https://patches.dpdk.org/project/dpdk/patch/20241012091457.21554-1-haijie1@huawei.com/
patch[3/4][4/4]
https://patches.dpdk.org/project/dpdk/cover/20241012091735.24012-1-haijie1@huawei.com/
> This patch set make clean codes.
>
> Chengwen Feng (4):
> ethdev: verify queue ID when Tx done cleanup
> net/hns3: verify reset type from firmware
> dmadev: fix potential null pointer access
> dmadev: clean code for verify parameter
>
> drivers/net/hns3/hns3_intr.c | 6 ++++++
> lib/dmadev/rte_dmadev.c | 32 +++++++++++++++++++++-----------
> lib/ethdev/rte_ethdev.c | 4 ++++
> 3 files changed, 31 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2024-10-12 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 6:46 Jie Hai
2024-09-05 6:46 ` [PATCH 1/4] ethdev: verify queue ID when Tx done cleanup Jie Hai
2024-09-05 7:33 ` Andrew Rybchenko
2024-10-12 2:27 ` Ferruh Yigit
2024-10-12 9:14 ` fengchengwen
2024-09-05 6:46 ` [PATCH 2/4] net/hns3: verify reset type from firmware Jie Hai
2024-09-05 6:46 ` [PATCH 3/4] dmadev: fix potential null pointer access Jie Hai
2024-09-05 6:46 ` [PATCH 4/4] dmadev: clean code for verify parameter Jie Hai
2024-10-12 9:31 ` Jie Hai [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=9ad96046-e503-6deb-3968-70455df63fcf@huawei.com \
--to=haijie1@huawei.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=lihuisong@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).