From: Thomas Monjalon <thomas@monjalon.net>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, "Awal,
Mohammad Abdul" <mohammad.abdul.awal@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes
Date: Mon, 13 May 2019 23:31:42 +0200 [thread overview]
Message-ID: <1639164.48bIzkVJc9@xps> (raw)
Message-ID: <20190513213142.Q4wn77NhAVSiOQU9F8iqDfTzFQ5BhoT0Cmd1JXY55hI@z> (raw)
In-Reply-To: <4998387.bMJ0bTz0iv@xps>
13/05/2019 16:12, Thomas Monjalon:
> 13/05/2019 15:59, Singh, Jasvinder:
> > From: Thomas Monjalon [mailto:thomas@monjalon.net]
> > > 29/04/2019 12:31, Mohammad Abdul Awal:
> > > > On 24/04/2019 13:37, Jasvinder Singh wrote:
> > > > > Add deprecation note for making changes in data structures, APIs and
> > > > > macros in order to have more traffic classes, flexible mapping of
> > > > > pipe queues to traffic classes, subport level configuration of pipes
> > > > > and queues, etc. These changes are aligned to improvements suggested
> > > > > in the RFC-
> > > > > https://mails.dpdk.org/archives/dev/2018-November/120035.html
> > > > >
> > > > > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> > > > > Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> > > > > ---
> > > > > --- a/doc/guides/rel_notes/deprecation.rst
> > > > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > > > +* sched: To allow more traffic classes, flexible mapping of pipe
> > > > > +queues to
> > > > > + traffic classes, and subport level configuration of pipes and
> > > > > +queues
> > > > > + changes will be made to macros, data structures and API functions
> > > > > +defined
> > > > > + in "rte_sched.h". These changes are aligned to improvements
> > > > > +suggested in the
> > > > > + RFC https://mails.dpdk.org/archives/dev/2018-November/120035.html.
> > >
> > > >
> > > > Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
> > > Acked-by : Reshma Pattan <reshma.pattan@intel.com>
> > >
> > > There are only 2 acks for this change.
> > > Any other opinion? yes or no?
> > >
> >
> > Cristian has provided his ack as well, please see below signed-off line.
>
> You are right.
> So we get enough acks from the whole team :)
>
> If nobody is against, I will merge it.
Applied, thanks
next prev parent reply other threads:[~2019-05-13 21:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 12:37 Jasvinder Singh
2019-04-24 12:37 ` Jasvinder Singh
2019-04-29 10:31 ` Mohammad Abdul Awal
2019-04-29 10:31 ` Mohammad Abdul Awal
2019-05-13 13:56 ` Thomas Monjalon
2019-05-13 13:56 ` Thomas Monjalon
2019-05-13 13:59 ` Singh, Jasvinder
2019-05-13 13:59 ` Singh, Jasvinder
2019-05-13 14:12 ` Thomas Monjalon
2019-05-13 14:12 ` Thomas Monjalon
2019-05-13 21:31 ` Thomas Monjalon [this message]
2019-05-13 21:31 ` Thomas Monjalon
2019-04-30 15:18 ` Pattan, Reshma
2019-04-30 15:18 ` Pattan, Reshma
2020-07-16 10:28 Savinay Dharmappa
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=1639164.48bIzkVJc9@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jasvinder.singh@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=stephen@networkplumber.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).