DPDK patches and discussions
 help / color / mirror / Atom feed
From: Chaoyong He <chaoyong.he@corigine.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: oss-drivers <oss-drivers@corigine.com>,
	Niklas Soderlund <niklas.soderlund@corigine.com>
Subject: RE: [PATCH v3 0/3] announce bonding macro and function change
Date: Wed, 26 Jul 2023 09:06:55 +0000	[thread overview]
Message-ID: <SJ0PR13MB55453D46465740340F89B4F89E00A@SJ0PR13MB5545.namprd13.prod.outlook.com> (raw)
In-Reply-To: <20230718082856.2235450-1-chaoyong.he@corigine.com>

A gentle ping~

Could anyone kindly enough give us a 4th 'Acked-by' to make it can be merged into v23.07?

Thanks very much!

> -----Original Message-----
> From: Chaoyong He
> Sent: Tuesday, July 18, 2023 4:29 PM
> To: dev@dpdk.org
> Cc: oss-drivers <oss-drivers@corigine.com>; Niklas Soderlund
> <niklas.soderlund@corigine.com>; Chaoyong He
> <chaoyong.he@corigine.com>
> Subject: [PATCH v3 0/3] announce bonding macro and function change
> 
> 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.
> 
> ---
> v3:
> * Adjust the statement in 'deprecation.rst' document.
> v2:
> * Drop the rename of function and data struct in the logics.
> ---
> 
> Chaoyong He (2):
>   doc: announce bonding data change
>   doc: announce bonding function change
> 
> Long Wu (1):
>   doc: announce bonding macro change
> 
>  app/test-pmd/testpmd.c                 |  2 +-
>  doc/guides/rel_notes/deprecation.rst   | 17 +++++++++++++++++
>  drivers/net/bonding/rte_eth_bond_api.c |  6 +++---
>  lib/ethdev/rte_ethdev.h                |  5 +++--
>  4 files changed, 24 insertions(+), 6 deletions(-)
> 
> --
> 2.39.1


  parent reply	other threads:[~2023-07-26  9:07 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  8:15 [PATCH " 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     ` [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     ` Chaoyong He [this message]
2023-07-28 13:54     ` [PATCH v3 0/3] announce bonding macro and " 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=SJ0PR13MB55453D46465740340F89B4F89E00A@SJ0PR13MB5545.namprd13.prod.outlook.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).