From: Akhil Goyal <akhil.goyal@nxp.com>
To: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "fiona.trahe@intel.com" <fiona.trahe@intel.com>,
Adam Dybkowski <adamx.dybkowski@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>,
Adam Dybkowski <adamx.dybkowski@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"anatoly.burakov@intel.com" <anatoly.burakov@intel.com>,
"bluca@debian.org" <bluca@debian.org>
Subject: Re: [dpdk-dev] [PATCH] doc: scheduler API deprecation notice
Date: Thu, 6 Aug 2020 17:18:32 +0000 [thread overview]
Message-ID: <VI1PR04MB316802782A7A973800B556BEE6480@VI1PR04MB3168.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <6007410.jhkHcQHMhq@thomas>
> 27/07/2020 11:41, Adam Dybkowski:
> > This patch adds a deprecation notice about upcoming changes
> > in public API of the Scheduler PMD.
> >
> > Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> > Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
> > ---
> > +* scheduler: The functions ``rte_cryptodev_scheduler_slave_attach``,
> > + ``rte_cryptodev_scheduler_slave_detach`` and
> > + ``rte_cryptodev_scheduler_slaves_get`` will be replaced in 20.11 by
> > + ``rte_cryptodev_scheduler_worker_attach``,
> > + ``rte_cryptodev_scheduler_worker_detach`` and
> > + ``rte_cryptodev_scheduler_workers_get`` accordingly.
>
> Acked-by: Thomas Monjalon <thomas@monjalon.net>
>
I wonder how this patch got missed.
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
next prev parent reply other threads:[~2020-08-06 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:41 Adam Dybkowski
2020-08-06 14:21 ` Thomas Monjalon
2020-08-06 17:18 ` Akhil Goyal [this message]
2020-08-07 22:05 ` Thomas Monjalon
2020-08-10 9:47 ` Dybkowski, AdamX
2020-08-10 10:19 ` Thomas Monjalon
2020-08-10 11:49 ` Trahe, Fiona
2020-08-10 12:50 ` Thomas Monjalon
2020-08-12 9:52 ` Bruce Richardson
2020-08-12 10:22 ` Thomas Monjalon
2020-08-12 10:49 ` [dpdk-dev] [dpdk-techboard] " Maxime Coquelin
2020-08-12 10:57 ` Hemant Agrawal
2020-08-12 12:23 ` Thomas Monjalon
2020-08-12 15:25 ` Stephen Hemminger
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=VI1PR04MB316802782A7A973800B556BEE6480@VI1PR04MB3168.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=adamx.dybkowski@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stephen@networkplumber.org \
--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).