From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes
Date: Tue, 30 Apr 2019 15:18:40 +0000 [thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A44C8B4@irsmsx110.ger.corp.intel.com> (raw)
Message-ID: <20190430151840.7FH5XBCKm4J-gV8iezhYJLahDfOzunonxNx6623lt6E@z> (raw)
In-Reply-To: <20190424123717.123541-1-jasvinder.singh@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jasvinder Singh
> Sent: Wednesday, April 24, 2019 1:37 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>
> Subject: [dpdk-dev] [PATCH] doc: add deprecation notice for sched changes
>
> 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>
Acked-by : Reshma Pattan <reshma.pattan@intel.com>
next prev parent reply other threads:[~2019-04-30 15:18 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
2019-05-13 21:31 ` Thomas Monjalon
2019-04-30 15:18 ` Pattan, Reshma [this message]
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=3AEA2BF9852C6F48A459DA490692831F2A44C8B4@irsmsx110.ger.corp.intel.com \
--to=reshma.pattan@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
/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).