From: Jie Hai <haijie1@huawei.com>
To: "lihuisong (C)" <lihuisong@huawei.com>, <dev@dpdk.org>,
Dongdong Liu <liudongdong3@huawei.com>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Lijun Ou <oulijun@huawei.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: Re: [PATCH 1/4] net/hns3: fix a typo
Date: Fri, 27 Oct 2023 14:20:31 +0800 [thread overview]
Message-ID: <876fa349-6531-0c40-6050-9af42c3b4cba@huawei.com> (raw)
In-Reply-To: <02b3e901-b100-8a67-ef2f-4bbc662cf8ca@huawei.com>
@all
The patch "[PATCH 1/4] net/hns3: fix a typo" has been moved to patchset
"[0/8] net/hns3: add some bugfix for hns3", see
https://patches.dpdk.org/project/dpdk/cover/20231027060947.3183983-1-haijie1@huawei.com/
On 2023/10/18 19:32, lihuisong (C) wrote:
> hns3 patch can be stripped from this series.
> ltgm,
> Acked-by: Huisong Li <lihuisong@huawei.com>
>
>
> 在 2023/10/18 9:39, Jie Hai 写道:
>> This patch fixes a typo.
>>
>> Fixes: c09c7847d892 ("net/hns3: support traffic management")
>> Cc: stable@dpdk.org
>>
>> Signed-off-by: Jie Hai <haijie1@huawei.com>
>> ---
>> drivers/net/hns3/hns3_tm.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/hns3/hns3_tm.c b/drivers/net/hns3/hns3_tm.c
>> index 67402a700f46..d9691640140b 100644
>> --- a/drivers/net/hns3/hns3_tm.c
>> +++ b/drivers/net/hns3/hns3_tm.c
>> @@ -739,7 +739,7 @@ hns3_tm_node_type_get(struct rte_eth_dev *dev,
>> uint32_t node_id,
>> }
>> static void
>> -hns3_tm_nonleaf_level_capsbilities_get(struct rte_eth_dev *dev,
>> +hns3_tm_nonleaf_level_capabilities_get(struct rte_eth_dev *dev,
>> uint32_t level_id,
>> struct rte_tm_level_capabilities *cap)
>> {
>> @@ -818,7 +818,7 @@ hns3_tm_level_capabilities_get(struct rte_eth_dev
>> *dev,
>> memset(cap, 0, sizeof(struct rte_tm_level_capabilities));
>> if (level_id != HNS3_TM_NODE_LEVEL_QUEUE)
>> - hns3_tm_nonleaf_level_capsbilities_get(dev, level_id, cap);
>> + hns3_tm_nonleaf_level_capabilities_get(dev, level_id, cap);
>> else
>> hns3_tm_leaf_level_capabilities_get(dev, cap);
> .
next prev parent reply other threads:[~2023-10-27 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 1:39 [PATCH 0/4] add telemetry commands for TM capabilities Jie Hai
2023-10-18 1:39 ` [PATCH 1/4] net/hns3: fix a typo Jie Hai
2023-10-18 11:32 ` lihuisong (C)
2023-10-27 6:20 ` Jie Hai [this message]
2023-10-18 1:39 ` [PATCH 2/4] ethdev: add telemetry command for TM capabilities Jie Hai
2023-10-18 1:39 ` [PATCH 3/4] ethdev: add telemetry command for TM level capabilities Jie Hai
2023-10-18 1:39 ` [PATCH 4/4] ethdev: add telemetry command for TM node capabilities Jie Hai
2023-10-18 10:50 ` [PATCH 0/4] add telemetry commands for TM capabilities fengchengwen
2023-10-25 1:47 ` Jie Hai
2023-10-31 15:30 ` Ferruh Yigit
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=876fa349-6531-0c40-6050-9af42c3b4cba@huawei.com \
--to=haijie1@huawei.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liudongdong3@huawei.com \
--cc=oulijun@huawei.com \
--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).