From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Huisong Li" <lihuisong@huawei.com>, <dev@dpdk.org>
Cc: <bruce.richardson@intel.com>, <hkalra@marvell.com>,
<huangdaode@huawei.com>, <fengchengwen@huawei.com>
Subject: RE: [PATCH v2] mem: fix displaying heap ID failed for heap info command
Date: Wed, 22 Feb 2023 08:53:29 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D87767@smartserver.smartshare.dk> (raw)
In-Reply-To: <20230222074953.22715-1-lihuisong@huawei.com>
> From: Huisong Li [mailto:lihuisong@huawei.com]
> Sent: Wednesday, 22 February 2023 08.50
o command
>
> The telemetry lib has added a allowed characters set for dictionary names.
> Please see commit 2537fb0c5f34 ("telemetry: limit characters allowed in
> dictionary names")
>
> The space is not in this set, which cause the heap ID in /eal/heap_info
> cannot be displayed. Additionally, 'heap' is also misspelling. So use
> 'Heap_id' to replace 'Head id'.
>
> Fixes: e6732d0d6e26 ("mem: add telemetry infos")
> Fixes: 2537fb0c5f34 ("telemetry: limit characters allowed in dictionary
> names")
> Cc: stable@dpdk.org
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Acked-by: Chengwen Feng <fengchengwen@huawei.com>
> ---
Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2023-02-22 7:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 3:03 [PATCH] " Huisong Li
2023-02-09 3:23 ` fengchengwen
2023-02-09 8:48 ` David Marchand
2023-02-11 2:58 ` lihuisong (C)
2023-02-11 3:04 ` lihuisong (C)
2023-02-22 7:49 ` [PATCH v2] " Huisong Li
2023-02-22 7:53 ` Morten Brørup [this message]
2023-03-12 8:40 ` Thomas Monjalon
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=98CBD80474FA8B44BF855DF32C47DC35D87767@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=hkalra@marvell.com \
--cc=huangdaode@huawei.com \
--cc=lihuisong@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).