From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 9CB1C48AE0; Tue, 11 Nov 2025 19:25:10 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 6054B40280; Tue, 11 Nov 2025 19:25:10 +0100 (CET) Received: from fout-b5-smtp.messagingengine.com (fout-b5-smtp.messagingengine.com [202.12.124.148]) by mails.dpdk.org (Postfix) with ESMTP id 1116F4026D; Tue, 11 Nov 2025 19:25:09 +0100 (CET) Received: from phl-compute-07.internal (phl-compute-07.internal [10.202.2.47]) by mailfout.stl.internal (Postfix) with ESMTP id 47ED31D00170; Tue, 11 Nov 2025 13:25:08 -0500 (EST) Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-07.internal (MEProxy); Tue, 11 Nov 2025 13:25:08 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm3; t=1762885508; x=1762971908; bh=M49hjSQ3GKqX2vpcSIqthSotioT7mPEl0VgLxfpo+q8=; b= klySV3CVg6l0COSJJWoapUdVGZpJ5g3o6kyc2W6dngRrgmbqoJ0TK+JiOLs7Ca86 4rhQcu+P+dE3Xvji+2gHv7ar4/A/9uI4R1X+scBUMwnn+SQalelMRXnJrm30iWx9 s8HRRa/kkk09IE9hDmqjeZ42P9tYK8i/QEl2zBdQ49rH5aor7R7hD/yZVHNcrpny KqY9KKgfIwCwsNKVxOTuSH1CQLFav6lRJPUpCegXjUvukVXED01RAtRDRkOw2fwu 9CjFE6h06GezndBBvExTHAFO4vMxwe9R/BRQGkyLPqVQg/pQ9BmdAKyQ00YQQdi0 CbdmMR8Si/m9AXYLnJwWxg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1762885508; x= 1762971908; bh=M49hjSQ3GKqX2vpcSIqthSotioT7mPEl0VgLxfpo+q8=; b=1 ikuOe+AkX25O/Omdu4sqWLsOzljfIkZyWR5FWp1ZVsF69eNiziSvJ2DgWSFmay56 bNg6cl13C1JZurIQJuLg/bV9qrS4N6ZmwvKrQr2zMI8oeUZFK4FW2waoQfAA8+yL oQToRcQj5PjpF/QO9RvCAVF4vgiVABNiFObcRBmbI6hMA01lStJtFARPDS9GfvVI A97nnDjT1fxqvRY7YRv7aWAWv4NtSG2ZQ0vBumE7bp1T6uLt7pf9hlFtvBUI1ZsU f+UaVRKoDIfdleLSFEtVSWTFkgFytFtF9eqYrwZiY+R7XQrSxmB65KmDDd2jzviz dHAJaxwemUmMNkZOuniGQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeffedrtdeggddvtdduledtucetufdoteggodetrf dotffvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfurfetoffkrfgpnffqhgenuceu rghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujf gurhephffvvefufffkjghfggfgtgesthfuredttddtjeenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeejudevheeiveduuddtveffgfdtgeekueevjeffjeegtdeggeekgfdv uefgfeekjeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopedufedp mhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepshhivhgrphhrrghsrggurdhtuhhmmh grlhgrsegrmhgurdgtohhmpdhrtghpthhtohepshhtrggslhgvseguphgukhdrohhrghdp rhgtphhtthhopehmsgesshhmrghrthhshhgrrhgvshihshhtvghmshdrtghomhdprhgtph htthhopegurghvihgurdhmrghrtghhrghnugesrhgvughhrghtrdgtohhmpdhrtghpthht ohepkhhtrhgrhihnohhrsehrvgguhhgrthdrtghomhdprhgtphhtthhopehkohhnshhtrg hnthhinhdrrghnrghnhigvvheshhhurgifvghirdgtohhmpdhrtghpthhtohepkhhonhhs thgrnhhtihhnrdhvrdgrnhgrnhihvghvseihrghnuggvgidrrhhupdhrtghpthhtohepmh grgihimhgvrdgtohhquhgvlhhinhesrhgvughhrghtrdgtohhmpdhrtghpthhtoheprggt ohhnohhlvgesrhgvughhrghtrdgtohhm X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 11 Nov 2025 13:25:05 -0500 (EST) From: Thomas Monjalon To: Sivaprasad Tummala Cc: stable@dpdk.org, mb@smartsharesystems.com, david.marchand@redhat.com, ktraynor@redhat.com, konstantin.ananyev@huawei.com, konstantin.v.ananyev@yandex.ru, maxime.coquelin@redhat.com, aconole@redhat.com, ferruh.yigit@amd.com, dev@dpdk.org, ciara.power@intel.com, Bruce Richardson Subject: Re: [PATCH] examples/l3fwd-power: fix telemetry command registration Date: Tue, 11 Nov 2025 19:25:04 +0100 Message-ID: <5662854.jrt8l4j9yI@thomas> In-Reply-To: References: <20251006101058.191495-1-sivaprasad.tummala@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 06/11/2025 14:41, Bruce Richardson: > On Mon, Oct 06, 2025 at 10:10:58AM +0000, Sivaprasad Tummala wrote: > > Telemetry command registration fails if the command name contains > > characters other than alphanumeric, underscore (_), and forward > > slash (/). > > > > The l3fwd-power example previously used "/l3fwd-power/stats" > > as telemetry command, which includes a hyphen (-) and causes > > registration failure. > > > > This patch fixes the issue by replacing the hyphen with an > > underscore, changing the command to "/l3fwd_power/stats" > > > > Fixes: a35919a1139b ("examples/l3fwd-power: use new telemetry") > > Cc: ciara.power@intel.com > > Cc: stable@dpdk.org > > > > Signed-off-by: Sivaprasad Tummala > Acked-by: Bruce Richardson Applied, thanks.