From: Nithin Dabilpuram <ndabilpuram@marvell.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: <bruce.richardson@intel.com>, <cristian.dumitrescu@intel.com>,
<thomas@monjalon.net>, <bluca@debian.org>,
<jasvinder.singh@intel.com>, <arybchenko@solarflare.com>,
<ray.kinsella@intel.com>, <nhorman@tuxdriver.com>,
<ktraynor@redhat.com>, <david.marchand@redhat.com>,
Ray Kinsella <mdr@ashroe.eu>, <dev@dpdk.org>,
<jerinj@marvell.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH v2] ethdev: mark all traffic manager API as experimental
Date: Thu, 10 Sep 2020 15:21:51 +0530 [thread overview]
Message-ID: <20200910095151.GA25338@outlook.office365.com> (raw)
In-Reply-To: <1123dd1e-6f17-fa63-4956-ab7493c22c31@intel.com>
On Thu, Sep 10, 2020 at 09:36:14AM +0100, Ferruh Yigit wrote:
> External Email
>
> ----------------------------------------------------------------------
> On 9/10/2020 9:05 AM, Nithin Dabilpuram wrote:
> > This patch marks all traffic manager API as experimental as
> > per discussion mentioned in below thread.
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__mails.dpdk.org_archives_dev_2020-2DApril_165364.html&d=DwIDaQ&c=nKjWec2b6R0mOyPaz7xtfQ&r=FZ_tPCbgFOh18zwRPO9H0yDx8VW38vuapifdDfc8SFQ&m=wqVBW8b3o-0Gamt8jyb4qjfv2NC91yJu72NYGkTiV_Q&s=-2I-O0kTUtPiOhpNsG_7Z06p9jn_h55ZQuO-KW6h-R4&e=
> >
> > Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> > ---
> >
> > v2:
> > - Updated commit message.
>
>
> Hi Nithin Kumar,
>
> Perhaps there was a misunderstanding, the paragraph in the deprecation note
> documents about making tm APIs experimental needs to be removed, since it won't
> be valid anymore after this patch.
> And best place to remove that note is this patch.
Apologies for misunderstanding your statement. Will send a V3 with the same.
next prev parent reply other threads:[~2020-09-10 9:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 17:16 [dpdk-dev] [PATCH] doc: deprication notice to mark tm spec " 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
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 ` Nithin Dabilpuram [this message]
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=20200910095151.GA25338@outlook.office365.com \
--to=ndabilpuram@marvell.com \
--cc=arybchenko@solarflare.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=cristian.dumitrescu@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=ktraynor@redhat.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.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).