From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: Chaoyong He <chaoyong.he@corigine.com>
Cc: dev@dpdk.org, oss-drivers@corigine.com, niklas.soderlund@corigine.com
Subject: Re: [PATCH] doc: announce inclusive naming function name changes
Date: Fri, 19 May 2023 13:05:26 -0700 [thread overview]
Message-ID: <20230519200526.GB22897@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <20230519063334.1645933-1-chaoyong.he@corigine.com>
On Fri, May 19, 2023 at 02:33:34PM +0800, Chaoyong He wrote:
> 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>
> ---
Acked-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
next prev parent reply other threads:[~2023-05-19 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 6:33 Chaoyong He
2023-05-19 9:02 ` Ferruh Yigit
2023-05-19 16:12 ` Stephen Hemminger
2023-05-19 20:05 ` Tyler Retzlaff [this message]
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=20230519200526.GB22897@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.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).