DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Nithin Dabilpuram <nithind1988@gmail.com>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	"bluca@debian.org" <bluca@debian.org>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>,
	"arybchenko@solarflare.com" <arybchenko@solarflare.com>,
	"Kinsella, Ray" <ray.kinsella@intel.com>,
	"nhorman@tuxdriver.com" <nhorman@tuxdriver.com>,
	"ktraynor@redhat.com" <ktraynor@redhat.com>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "kkanas@marvell.com" <kkanas@marvell.com>,
	Nithin Dabilpuram <ndabilpuram@marvell.com>
Subject: Re: [dpdk-dev] [PATCH v2] doc: deprication notice to mark tm spec as experimental
Date: Tue, 5 May 2020 08:55:05 +0000	[thread overview]
Message-ID: <BYAPR11MB29350D481BE7B6709FA24515EBA70@BYAPR11MB2935.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200505080734.30726-1-nithind1988@gmail.com>



> -----Original Message-----
> From: Nithin Dabilpuram <nithind1988@gmail.com>
> Sent: Tuesday, May 5, 2020 9:08 AM
> To: Yigit, Ferruh <ferruh.yigit@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>; thomas@monjalon.net;
> bluca@debian.org; Singh, Jasvinder <jasvinder.singh@intel.com>;
> arybchenko@solarflare.com; Kinsella, Ray <ray.kinsella@intel.com>;
> nhorman@tuxdriver.com; ktraynor@redhat.com;
> david.marchand@redhat.com; Mcnamara, John
> <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Cc: dev@dpdk.org; jerinj@marvell.com; kkanas@marvell.com; Nithin
> Dabilpuram <ndabilpuram@marvell.com>
> Subject: [PATCH v2] doc: deprication notice to mark tm spec as experimental
> 
> From: Nithin Dabilpuram <ndabilpuram@marvell.com>
> 
> Based on the discussion in mail thread, it is concluded that
> all traffic manager API's (rte_tm.h) need to be marked experimental
> till few more releases to support further improvements to spec.
> 
> https://mails.dpdk.org/archives/dev/2020-April/164970.html
> 
> Adding deprication notice for the same in advance.
> 
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> ---
>  doc/guides/rel_notes/deprecation.rst | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 1339f54..2c76f36 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -118,3 +118,10 @@ Deprecation Notices
>    Python 2 support will be completely removed in 20.11.
>    In 20.08, explicit deprecation warnings will be displayed when running
>    scripts with Python 2.
> +
> +* traffic manager: All traffic manager API's in ``rte_tm.h`` were mistakenly
> made
> +  abi stable in the v19.11 release. The TM maintainer and other contributor's
> have
> +  agreed to keep the TM API's as experimental in expectation of additional
> spec
> +  improvements. Therefore, all API's in ``rte_tm.h`` will be marked back as
> +  experimental in v20.11 DPDK release. For more details, please see `the
> thread
> +  <https://mails.dpdk.org/archives/dev/2020-April/164970.html>`_.
> --
> 2.8.4

Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>


  parent reply	other threads:[~2020-05-05  8:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 17:16 [dpdk-dev] [PATCH] " Nithin Dabilpuram
2020-05-05  6:47 ` Ray Kinsella
2020-05-05  7:45   ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-05-05  8:07 ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
2020-05-05  8:10   ` Ray Kinsella
2020-05-05  8:55   ` Dumitrescu, Cristian [this message]
2020-05-21 10:49     ` Jerin Jacob
2020-05-24 20:58       ` Nithin Kumar D
2020-05-24 23:33       ` Thomas Monjalon
2020-09-09 17:22 ` [dpdk-dev] [PATCH] ethdev: mark all traffic manager API " Nithin Dabilpuram
2020-09-09 17:49   ` Dumitrescu, Cristian
2020-09-09 18:23   ` Ferruh Yigit
2020-09-10  8:05   ` [dpdk-dev] [PATCH v2] " Nithin Dabilpuram
2020-09-10  8:30     ` Kinsella, Ray
2020-09-10 10:56       ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10 11:01         ` Kinsella, Ray
2020-09-10 11:22           ` Nithin Dabilpuram
2020-09-10  8:36     ` [dpdk-dev] " Ferruh Yigit
2020-09-10  8:37       ` Dumitrescu, Cristian
2020-09-10  9:54         ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10  9:51       ` [dpdk-dev] [EXT] " Nithin Dabilpuram
2020-09-10 10:09   ` [dpdk-dev] [PATCH v3] " Nithin Dabilpuram
2020-09-10 11:34     ` Ferruh Yigit

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=BYAPR11MB29350D481BE7B6709FA24515EBA70@BYAPR11MB2935.namprd11.prod.outlook.com \
    --to=cristian.dumitrescu@intel.com \
    --cc=arybchenko@solarflare.com \
    --cc=bluca@debian.org \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jasvinder.singh@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=kkanas@marvell.com \
    --cc=ktraynor@redhat.com \
    --cc=marko.kovacevic@intel.com \
    --cc=ndabilpuram@marvell.com \
    --cc=nhorman@tuxdriver.com \
    --cc=nithind1988@gmail.com \
    --cc=ray.kinsella@intel.com \
    --cc=thomas@monjalon.net \
    /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).