From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jie Hai <haijie1@huawei.com>, dev@dpdk.org, thomas@monjalon.net
Cc: lihuisong@huawei.com, fengchengwen@huawei.com, huangdengdui@huawei.com
Subject: Re: [PATCH 0/2] net/hns3: bugfix for hns3
Date: Sun, 10 Nov 2024 22:52:26 +0000 [thread overview]
Message-ID: <c95642d4-f341-4498-8309-3d01196e70f7@amd.com> (raw)
In-Reply-To: <20241107115645.22617-1-haijie1@huawei.com>
On 11/7/2024 11:56 AM, Jie Hai wrote:
> This patchset fixes some bugs.
>
> Dengdui Huang (2):
> net/hns3: fix error code for repeatedly create counter
> net/hns3: fix cannot fully use hardware flow director table
>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-11-10 22:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:56 Jie Hai
2024-11-07 11:56 ` [PATCH 1/2] net/hns3: fix error code for repeatedly create counter Jie Hai
2024-11-07 16:21 ` Stephen Hemminger
2024-11-07 11:56 ` [PATCH 2/2] net/hns3: fix cannot fully use hardware flow director table Jie Hai
2024-11-07 16:21 ` Stephen Hemminger
2024-11-10 22:52 ` 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=c95642d4-f341-4498-8309-3d01196e70f7@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.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).