From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
Chaoyong He <chaoyong.he@corigine.com>,
Long Wu <long.wu@corigine.com>
Subject: [PATCH v3 3/3] doc: announce bonding function change
Date: Tue, 18 Jul 2023 16:28:56 +0800 [thread overview]
Message-ID: <20230718082856.2235450-4-chaoyong.he@corigine.com> (raw)
In-Reply-To: <20230718082856.2235450-1-chaoyong.he@corigine.com>
In order to support inclusive naming, some of the function in DPDK will
need to be renamed. Do this through deprecation process now for 23.07.
Signed-off-by: Long Wu <long.wu@corigine.com>
Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
---
doc/guides/rel_notes/deprecation.rst | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8cf972a9ab..45da0361e6 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -123,6 +123,17 @@ Deprecation Notices
``RTE_ETH_DEV_BONDING_MEMBER``.
The data structure ``struct rte_eth_bond_8023ad_slave_info`` will be
renamed to ``struct rte_eth_bond_8023ad_member_info`` in DPDK 23.11.
+ The following functions will be removed in DPDK 23.11. The old functions:
+ ``rte_eth_bond_8023ad_slave_info``,
+ ``rte_eth_bond_active_slaves_get``,
+ ``rte_eth_bond_slave_add``,
+ ``rte_eth_bond_slave_remove``, and
+ ``rte_eth_bond_slaves_get`` will be replaced by:
+ ``rte_eth_bond_8023ad_member_info``,
+ ``rte_eth_bond_active_members_get``,
+ ``rte_eth_bond_member_add``,
+ ``rte_eth_bond_member_remove``, and
+ ``rte_eth_bond_members_get``.
* cryptodev: The function ``rte_cryptodev_cb_fn`` will be updated
to have another parameter ``qp_id`` to return the queue pair ID
--
2.39.1
next prev parent reply other threads:[~2023-07-18 8:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:15 [PATCH 0/3] announce bonding macro and " Chaoyong He
2023-07-14 8:15 ` [PATCH 1/3] doc: announce bonding macro change Chaoyong He
2023-07-17 15:13 ` Ferruh Yigit
2023-07-18 1:17 ` Chaoyong He
2023-07-14 8:15 ` [PATCH 2/3] doc: announce bonding data change Chaoyong He
2023-07-17 15:03 ` Ferruh Yigit
2023-07-18 1:13 ` Chaoyong He
2023-07-14 8:15 ` [PATCH 3/3] doc: announce bonding function change Chaoyong He
2023-07-17 15:13 ` Ferruh Yigit
2023-07-18 1:15 ` Chaoyong He
2023-07-17 15:14 ` [PATCH 0/3] announce bonding macro and " Ferruh Yigit
2023-07-18 1:48 ` [PATCH v2 " Chaoyong He
2023-07-18 1:48 ` [PATCH v2 1/3] doc: announce bonding macro change Chaoyong He
2023-07-18 8:09 ` Ferruh Yigit
2023-07-18 1:48 ` [PATCH v2 2/3] doc: announce bonding data change Chaoyong He
2023-07-18 8:05 ` Ferruh Yigit
2023-07-18 1:48 ` [PATCH v2 3/3] doc: announce bonding function change Chaoyong He
2023-07-18 8:05 ` Ferruh Yigit
2023-07-18 8:28 ` [PATCH v3 0/3] announce bonding macro and " Chaoyong He
2023-07-18 8:28 ` [PATCH v3 1/3] doc: announce bonding macro change Chaoyong He
2023-07-18 11:39 ` Ferruh Yigit
2023-07-18 15:53 ` Stephen Hemminger
2023-07-19 1:24 ` lihuisong (C)
2023-07-26 11:47 ` Morten Brørup
2023-07-18 8:28 ` [PATCH v3 2/3] doc: announce bonding data change Chaoyong He
2023-07-18 11:40 ` Ferruh Yigit
2023-07-18 15:53 ` Stephen Hemminger
2023-07-19 1:32 ` lihuisong (C)
2023-07-18 8:28 ` Chaoyong He [this message]
2023-07-18 11:40 ` [PATCH v3 3/3] doc: announce bonding function change Ferruh Yigit
2023-07-18 15:52 ` Stephen Hemminger
2023-07-19 1:31 ` lihuisong (C)
2023-07-19 1:37 ` Chaoyong He
2023-07-19 1:53 ` lihuisong (C)
2023-07-26 9:06 ` [PATCH v3 0/3] announce bonding macro and " Chaoyong He
2023-07-28 13:54 ` Thomas Monjalon
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=20230718082856.2235450-4-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--cc=long.wu@corigine.com \
--cc=niklas.soderlund@corigine.com \
--cc=oss-drivers@corigine.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).