From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Chaoyong He <chaoyong.he@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH 0/3] announce bonding macro and function change
Date: Mon, 17 Jul 2023 16:14:03 +0100 [thread overview]
Message-ID: <5b793feb-8fda-a913-ccbe-9606ea976507@amd.com> (raw)
In-Reply-To: <20230714081526.1277786-1-chaoyong.he@corigine.com>
On 7/14/2023 9:15 AM, Chaoyong He wrote:
> In order to support inclusive naming, some of the macro and function in
> DPDK will need to be renamed. Do this through deprecation process now
> for 23.07.
>
> Chaoyong He (2):
> doc: announce bonding data change
> doc: announce bonding function change
>
> Long Wu (1):
> doc: announce bonding macro change
Hi Chaoyong,
OK to deprecate macro in this release (v23.07) and remove them in LTS
(v23.11) release,
but for struct and function names I think simpler to rename them
directly in LTS release without deprecating them in this release, more
details in the individual patches.
next prev parent reply other threads:[~2023-07-17 15:14 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 8:15 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 ` Ferruh Yigit [this message]
2023-07-18 1:48 ` [PATCH v2 0/3] announce bonding macro and " 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 ` [PATCH v3 3/3] doc: announce bonding function change Chaoyong He
2023-07-18 11:40 ` 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=5b793feb-8fda-a913-ccbe-9606ea976507@amd.com \
--to=ferruh.yigit@amd.com \
--cc=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).