From: "lihuisong (C)" <lihuisong@huawei.com>
To: Jie Hai <haijie1@huawei.com>, <dev@dpdk.org>
Cc: <huangdengdui@huawei.com>,
Chengwen Feng <fengchengwen@huawei.com>, <ferruh.yigit@amd.com>,
<thomas@monjalon.net>
Subject: Re: [PATCH v2 1/2] net/hns3: fix variable type
Date: Wed, 23 Oct 2024 14:32:36 +0800 [thread overview]
Message-ID: <fce91b86-d14e-32df-ae97-3def07e3c50c@huawei.com> (raw)
In-Reply-To: <20241022040113.2746-2-haijie1@huawei.com>
Acked-by: Huisong Li <lihuisong@huawei.com>
在 2024/10/22 12:01, Jie Hai 写道:
> The patch fixes variable type in case of data trunction.
>
> Fixes: dd4b8bba785f ("net/hns3: support reporting names of registers")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
> ---
> drivers/net/hns3/hns3_regs.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/hns3/hns3_regs.c b/drivers/net/hns3/hns3_regs.c
> index e8bc7fbc66e1..be6929738942 100644
> --- a/drivers/net/hns3/hns3_regs.c
> +++ b/drivers/net/hns3/hns3_regs.c
> @@ -1178,9 +1178,9 @@ hns3_direct_access_tqp_regs_help(struct hns3_hw *hw, struct rte_dev_reg_info *re
> uint32_t modules, enum hns3_reg_modules idx)
> {
> const struct hns3_dirt_reg_entry *reg_list;
> - uint16_t tqp_num, reg_offset;
> + uint32_t reg_num, i, j, reg_offset;
> uint32_t *data = regs->data;
> - uint32_t reg_num, i, j;
> + uint16_t tqp_num;
>
> if ((modules & HNS3_MODULE_MASK(idx)) == 0)
> return;
next prev parent reply other threads:[~2024-10-23 6:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 2:00 [PATCH] " Jie Hai
2024-10-22 4:01 ` [PATCH v2 0/2] net/hns3: bugfix on register dump Jie Hai
2024-10-22 4:01 ` [PATCH v2 1/2] net/hns3: fix variable type Jie Hai
2024-10-22 6:32 ` fengchengwen
2024-10-23 6:32 ` lihuisong (C) [this message]
2024-10-22 4:01 ` [PATCH v2 2/2] net/hns3: fix pointer offset Jie Hai
2024-10-22 6:32 ` fengchengwen
2024-10-23 6:32 ` lihuisong (C)
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=fce91b86-d14e-32df-ae97-3def07e3c50c@huawei.com \
--to=lihuisong@huawei.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@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).