From: Jie Hai <haijie1@huawei.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>, <dev@dpdk.org>
Cc: <fengchengwen@huawei.com>, <liudongdong3@huawei.com>,
<lihuisong@huawei.com>, <huangdengdui@huawei.com>
Subject: Re: [PATCH 0/8] net/hns3: add some bugfix for hns3
Date: Sat, 28 Oct 2023 09:57:28 +0800 [thread overview]
Message-ID: <1227a718-1e89-c884-7de4-685c35e44f36@huawei.com> (raw)
In-Reply-To: <5fc381bd-1b6a-4320-903c-fb586efbb912@amd.com>
On 2023/10/28 3:29, Ferruh Yigit wrote:
> On 10/27/2023 7:09 AM, Jie Hai wrote:
>> This patchset contains some bugfix for hns3 pmd.
>>
>> Dengdui Huang (6):
>> net/hns3: fix unchecked Rx free threshold
>> net/hns3: fix double stats for IMP and global reset
>> net/hns3: remove reset log in secondary
>> net/hns3: fix multiple reset detected log
>> net/hns3: fix the imp/global reset interrupted possibly
>> net/hns3: refactor interrupt state query
>>
>> Huisong Li (1):
>> net/hns3: fix segmentfault for NEON and SVE
>>
>> Jie Hai (1):
>> net/hns3: fix a typo
>>
>
> There is a checkpatch warning related to the atomics:
>
> ### [PATCH] net/hns3: fix multiple reset detected log
>
> Warning in drivers/net/hns3/hns3_ethdev.c:
> Using __atomic_xxx built-ins, prefer rte_atomic_xxx
>
> This is about update in the preferred atomic APIs, but as far as I can
> see patch doesn't add new atomic API but just changes the logic in the
> code, so I think we can ignore this warning for now,
> But please be aware of the guidance of the new atomic APIs, and take
> this into account for new code.
>
Thanks, and we will pay attention to it.
>
> Series applied to dpdk-next-net/main, thanks.
> .
prev parent reply other threads:[~2023-10-28 1:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 6:09 Jie Hai
2023-10-27 6:09 ` [PATCH 1/8] net/hns3: fix a typo Jie Hai
2023-10-27 6:09 ` [PATCH 2/8] net/hns3: fix unchecked Rx free threshold Jie Hai
2023-10-27 6:09 ` [PATCH 3/8] net/hns3: fix segmentfault for NEON and SVE Jie Hai
2023-10-27 6:09 ` [PATCH 4/8] net/hns3: fix double stats for IMP and global reset Jie Hai
2023-10-27 6:09 ` [PATCH 5/8] net/hns3: remove reset log in secondary Jie Hai
2023-10-27 6:09 ` [PATCH 6/8] net/hns3: fix multiple reset detected log Jie Hai
2023-10-27 6:09 ` [PATCH 7/8] net/hns3: fix the imp/global reset interrupted possibly Jie Hai
2023-10-27 6:09 ` [PATCH 8/8] net/hns3: refactor interrupt state query Jie Hai
2023-10-27 7:11 ` [PATCH 0/8] net/hns3: add some bugfix for hns3 fengchengwen
2023-10-27 19:29 ` Ferruh Yigit
2023-10-28 1:57 ` 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=1227a718-1e89-c884-7de4-685c35e44f36@huawei.com \
--to=haijie1@huawei.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=huangdengdui@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@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).