DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com,
	Long Wu <long.wu@corigine.com>,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: [PATCH] doc: announce inclusive naming macro name changes
Date: Wed,  7 Jun 2023 10:44:23 +0800	[thread overview]
Message-ID: <20230607024423.336664-1-chaoyong.he@corigine.com> (raw)

From: Long Wu <long.wu@corigine.com>

In order to support inclusive naming, some of the macro 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>
Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
---
Depends-on: patch-127084 ("doc: announce inclusive naming function name")
---
 doc/guides/rel_notes/deprecation.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 267a49aa13..67353d4f2b 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -175,3 +175,8 @@ Deprecation Notices
   ``rte_eth_bond_active_members_get``,
   ``rte_eth_bond_member_add``, ``rte_eth_bond_member_remove``,
   and ``rte_eth_bond_members_get``.
+  References to slave will be removed and replace bonded to bonding in DPDK 23.11.
+  The following macro will be deprecated in DPDK 23.07, and removed in DPDK 23.11.
+  The old macro:
+  ``RTE_ETH_DEV_BONDED_SLAVE`` will be replaced by:
+  ``RTE_ETH_DEV_BONDING_MEMBER``.
-- 
2.27.0


             reply	other threads:[~2023-06-07  2:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07  2:44 Chaoyong He [this message]
2023-06-07 15:01 ` Stephen Hemminger
2023-06-08  3:04 ` Xia, Chenbo
2023-07-13  3:22   ` Chaoyong He
2023-07-13  7:58 ` Ferruh Yigit

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=20230607024423.336664-1-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).