From: Thomas Monjalon <thomas@monjalon.net>
To: Jasvinder Singh <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>,
cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH] doc: deprecation notice for sched API change
Date: Sat, 24 Nov 2018 19:13:00 +0100 [thread overview]
Message-ID: <19051846.xPCahNV9hL@xps> (raw)
In-Reply-To: <533a742b-be09-8bcc-d469-7d29f8cf5018@intel.com>
21/11/2018 10:39, Mohammad Abdul Awal:
> On 14/11/2018 15:36, Jasvinder Singh wrote:
> > There will be change in API functions because of mbuf sched field
> > updates, outlined in deprecation note of mbuf->hash.sched.
> >
> > 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>
> Acked-by: Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Applied
prev parent reply other threads:[~2018-11-24 18:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 15:36 Jasvinder Singh
2018-11-16 16:10 ` Pattan, Reshma
2018-11-21 9:39 ` Mohammad Abdul Awal
2018-11-24 18:13 ` Thomas Monjalon [this message]
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=19051846.xPCahNV9hL@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=mohammad.abdul.awal@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).