From: Dongdong Liu <liudongdong3@huawei.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, <dev@dpdk.org>,
<thomas@monjalon.net>, <andrew.rybchenko@oktetlabs.ru>,
<fengchengwen@huawei.com>
Cc: <stable@dpdk.org>, <lihuisong@huawei.com>,
<yisen.zhuang@huawei.com>, <huangdengdui@huawei.com>
Subject: Re: [PATCH v2 0/5] net/hns3: add some features and bugfixes
Date: Thu, 1 Jun 2023 19:37:05 +0800 [thread overview]
Message-ID: <2d9edc96-f226-f840-b53b-7b17ff60f447@huawei.com> (raw)
In-Reply-To: <6b3e80d3-fc06-cfaa-189c-813f42713f11@amd.com>
Hi Ferruh
On 2023/6/1 18:30, Ferruh Yigit wrote:
> On 5/22/2023 5:15 PM, Ferruh Yigit wrote:
>> On 5/22/2023 2:17 PM, Dongdong Liu wrote:
>>> This patchset contains some features and bugfixes for hns3.
>>>
>>> v1->v2:
>>> -Fix check-git-log warnings.
>>>
>>> Chengwen Feng (1):
>>> net/hns3: fix receive multiple firmware reset interrupts
>>>
>>> Dengdui Huang (2):
>>> net/hns3: fix loop code variable type mismatch
>>> net/hns3: add Tx/Rx descriptor logs
>>>
>>> Huisong Li (2):
>>> net/hns3: fix never set MAC flow control
>>> net/hns3: add flow control autoneg for fiber port
>>>
>>
>> Series applied to dpdk-next-net/main, thanks.
>>
>
> There were multiple conflicts with previous "MAC flow control" feature,
> can you please double check the latest code in next-net?
I have checked the latest code in next-net, it looks good.
Thanks for helping to resolve the conflicts.
>
> Like in 'struct hns3_sfp_info_cmd', it wasn't clear which reserved field
> to use for 'fec_ability', after 'pause_status' split the reserved field
> into two, etc...
The latest code in next-net is right.
Thanks,
Dongdong.
> .
>
prev parent reply other threads:[~2023-06-01 11:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 11:29 [PATCH 0/5] ] " Dongdong Liu
2023-05-18 11:29 ` [PATCH 1/5] net/hns3: fix never set MAC flow control Dongdong Liu
2023-05-18 11:29 ` [PATCH 2/5] net/hns3: add flow control autoneg for fiber and backplane port Dongdong Liu
2023-05-18 11:29 ` [PATCH 3/5] net/hns3: fix loop code variable type mismatch Dongdong Liu
2023-05-18 11:29 ` [PATCH 4/5] net/hns3: fix receive multiple firmware reset interrupts Dongdong Liu
2023-05-18 11:29 ` [PATCH 5/5] net/hns3: add Tx/Rx descriptor logs Dongdong Liu
2023-05-22 11:57 ` [PATCH 0/5] ] net/hns3: add some features and bugfixes Ferruh Yigit
2023-05-22 12:13 ` Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 0/5] " Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 1/5] net/hns3: fix never set MAC flow control Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 2/5] net/hns3: add flow control autoneg for fiber port Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 3/5] net/hns3: fix loop code variable type mismatch Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 4/5] net/hns3: fix receive multiple firmware reset interrupts Dongdong Liu
2023-05-22 13:17 ` [PATCH v2 5/5] net/hns3: add Tx/Rx descriptor logs Dongdong Liu
2023-05-22 16:15 ` [PATCH v2 0/5] net/hns3: add some features and bugfixes Ferruh Yigit
2023-06-01 10:30 ` Ferruh Yigit
2023-06-01 11:37 ` Dongdong Liu [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=2d9edc96-f226-f840-b53b-7b17ff60f447@huawei.com \
--to=liudongdong3@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yisen.zhuang@huawei.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).