From: Adam Dybkowski <adamx.dybkowski@intel.com>
To: dev@dpdk.org, fiona.trahe@intel.com, akhil.goyal@nxp.com
Cc: Adam Dybkowski <adamx.dybkowski@intel.com>,
Fan Zhang <roy.fan.zhang@intel.com>
Subject: [dpdk-dev] [PATCH] doc: scheduler API deprecation notice
Date: Mon, 27 Jul 2020 11:41:13 +0200 [thread overview]
Message-ID: <20200727094113.2849-1-adamx.dybkowski@intel.com> (raw)
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>
---
doc/guides/rel_notes/deprecation.rst | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index a58a17946..dbc779a9e 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -142,3 +142,10 @@ Deprecation Notices
Python 2 support will be completely removed in 20.11.
In 20.08, explicit deprecation warnings will be displayed when running
scripts with Python 2.
+
+* 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.
--
2.25.1
next reply other threads:[~2020-07-27 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 9:41 Adam Dybkowski [this message]
2020-08-06 14:21 ` Thomas Monjalon
2020-08-06 17:18 ` Akhil Goyal
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=20200727094113.2849-1-adamx.dybkowski@intel.com \
--to=adamx.dybkowski@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=roy.fan.zhang@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).