From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Eelco Chaudron <echaudro@redhat.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] meter: move RFC4115 trTCM APIs as none experimental
Date: Tue, 17 Dec 2019 13:52:41 +0000 [thread overview]
Message-ID: <DM6PR11MB2714D3BF8AC2C8B8199FE478EB500@DM6PR11MB2714.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20191217130742.165886.15691.stgit@netdev64>
> -----Original Message-----
> From: Eelco Chaudron <echaudro@redhat.com>
> Sent: Tuesday, December 17, 2019 1:08 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Cc: stable@dpdk.org; dev@dpdk.org
> Subject: [PATCH] meter: move RFC4115 trTCM APIs as none experimental
>
> Moved RFC4115 APIs to none experimental as they have been there
> since 19.02. Also, these APIs are the same as the none RFC4115 APIs.
>
> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
> ---
> lib/librte_meter/rte_meter.h | 6 ------
> lib/librte_meter/rte_meter_version.map | 4 ++--
> 2 files changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/lib/librte_meter/rte_meter.h b/lib/librte_meter/rte_meter.h
> index d69b118..62c8c1e 100644
> --- a/lib/librte_meter/rte_meter.h
> +++ b/lib/librte_meter/rte_meter.h
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2019-12-17 13:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 13:07 [dpdk-dev] [PATCH] meter: move RFC4115 trTCM APIs as none experimental Eelco Chaudron
2019-12-17 13:52 ` Dumitrescu, Cristian [this message]
2020-01-20 15:17 ` Thomas Monjalon
2020-01-16 11:25 ` [dpdk-dev] [dpdk-stable] " David Marchand
2020-01-16 11:54 ` Neil Horman
2020-01-16 12:42 ` Ferruh Yigit
2020-01-16 14:38 ` Thomas Monjalon
2020-01-17 8:27 ` David Marchand
2020-01-17 10:46 ` Luca Boccassi
2020-01-22 13:55 ` Ray Kinsella
2020-01-30 16:33 ` Ray Kinsella
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=DM6PR11MB2714D3BF8AC2C8B8199FE478EB500@DM6PR11MB2714.namprd11.prod.outlook.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=echaudro@redhat.com \
--cc=stable@dpdk.org \
/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).