From: "Power, Ciara" <ciara.power@intel.com>
To: "Arshad, Samina" <samina.arshad@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Kearney, Tadhg" <tadhg.kearney@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"lihuisong@huawei.com" <lihuisong@huawei.com>,
"Dooley, Brian" <brian.dooley@intel.com>
Subject: RE: [PATCH v2] usertools/telemetry: fix unused parameter
Date: Thu, 25 May 2023 13:34:35 +0000 [thread overview]
Message-ID: <SN7PR11MB76396895FDA958B716309537E6469@SN7PR11MB7639.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20230523143855.218984-1-samina.arshad@intel.com>
Hi Samina,
> -----Original Message-----
> From: Arshad, Samina <samina.arshad@intel.com>
> Sent: Tuesday 23 May 2023 15:39
> To: y
> Cc: Power, Ciara <ciara.power@intel.com>; dev@dpdk.org; Kearney, Tadhg
> <tadhg.kearney@intel.com>; stable@dpdk.org; Arshad, Samina
> <samina.arshad@intel.com>; lihuisong@huawei.com
> Subject: [PATCH v2] usertools/telemetry: fix unused parameter
>
> This bug fix ensures that the runtime socket path is generated correctly, based
> on the user-specified file_prefix value, resolving the issue that occurred in the
> previous implementation.
>
> Fixes: a15fc792cfb6 ("usertools/telemetry: add file prefix argument")
> Cc: lihuisong@huawei.com
> Cc: stable@dpdk.org
No need for cc stable here because the bad commit was only introduced in 23.03 release.
That means we don't need the fix to be backported to 21.11 or 22.11, as the bug didn't exist in those releases.
+1 for code changes though,
Acked-by: Ciara Power <ciara.power@intel.com>
>
> Signed-off-by: Samina Arshad <samina.arshad@intel.com>
> ---
> v2:
> Made changes for previous commit to be efficient. Removed "args" from
> "args.file_prefix".
<snip>
next prev parent reply other threads:[~2023-05-25 13:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 13:47 [PATCH v1] " Samina Arshad
2023-05-23 14:38 ` [PATCH v2] " Samina Arshad
2023-05-25 13:34 ` Power, Ciara [this message]
2023-06-01 14:42 ` Thomas Monjalon
2023-06-01 14:52 ` Power, Ciara
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=SN7PR11MB76396895FDA958B716309537E6469@SN7PR11MB7639.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=brian.dooley@intel.com \
--cc=dev@dpdk.org \
--cc=lihuisong@huawei.com \
--cc=samina.arshad@intel.com \
--cc=stable@dpdk.org \
--cc=tadhg.kearney@intel.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).