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>
Subject: [PATCH] doc: announce inclusive naming function name changes
Date: Fri, 19 May 2023 14:33:34 +0800 [thread overview]
Message-ID: <20230519063334.1645933-1-chaoyong.he@corigine.com> (raw)
In order to support inclusive naming, some of the functions in
DPDK will need to be renamed. Do this through deprecation process
now for 23.07.
Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
---
doc/guides/rel_notes/deprecation.rst | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index dcc1ca1696..267a49aa13 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -163,3 +163,15 @@ Deprecation Notices
The new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status
starting with DPDK 23.07 release.
+
+* bonding: References to slave will be removed in DPDK 23.11. The following
+ functions will be deprecated in DPDK 23.07, and 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``.
--
2.39.1
next reply other threads:[~2023-05-19 6:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:33 Chaoyong He [this message]
2023-05-19 9:02 ` Ferruh Yigit
2023-05-19 16:12 ` Stephen Hemminger
2023-05-19 20:05 ` Tyler Retzlaff
2023-06-08 3:04 ` Xia, Chenbo
2023-07-04 2:21 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2023-03-31 18:51 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=20230519063334.1645933-1-chaoyong.he@corigine.com \
--to=chaoyong.he@corigine.com \
--cc=dev@dpdk.org \
--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).