From: "Power, Ciara" <ciara.power@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [PATCH 21.11] telemetry: remove experimental tags from APIs
Date: Mon, 5 Jul 2021 10:09:38 +0000 [thread overview]
Message-ID: <MN2PR11MB3821C51AD37E49DCAADE6520E61C9@MN2PR11MB3821.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20210702152305.606933-1-bruce.richardson@intel.com>
>-----Original Message-----
>From: Richardson, Bruce <bruce.richardson@intel.com>
>Sent: Friday 2 July 2021 16:23
>To: dev@dpdk.org
>Cc: Ray Kinsella <mdr@ashroe.eu>; Power, Ciara <ciara.power@intel.com>;
>Richardson, Bruce <bruce.richardson@intel.com>
>Subject: [PATCH 21.11] telemetry: remove experimental tags from APIs
>
>The telemetry APIs have been present and unchanged for >1 year now, so
>remove experimental tag from them.
>
>Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>---
> lib/telemetry/rte_telemetry.h | 18 ------------------
> lib/telemetry/version.map | 2 +-
> 2 files changed, 1 insertion(+), 19 deletions(-)
>
<snip>
Hi Bruce,
+1 for this change.
I think there are some experimental tags missing from this patch - the legacy telemetry functions that are in "metrics/rte_metrics_telemetry.h" currently have the tags too.
Also, there is a reference to the library being experimental in the Telemetry User Guide doc.
Thanks,
Ciara
next prev parent reply other threads:[~2021-07-05 10:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 15:23 Bruce Richardson
2021-07-05 10:09 ` Power, Ciara [this message]
2021-07-05 10:58 ` Bruce Richardson
2021-09-15 16:55 ` [dpdk-dev] [PATCH v2] " Bruce Richardson
2021-09-16 8:13 ` Power, Ciara
2021-09-27 13:03 ` Kinsella, Ray
2021-10-01 15:10 ` 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=MN2PR11MB3821C51AD37E49DCAADE6520E61C9@MN2PR11MB3821.namprd11.prod.outlook.com \
--to=ciara.power@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mdr@ashroe.eu \
/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).