DPDK patches and discussions
 help / color / mirror / Atom feed
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,
	Long Wu <long.wu@corigine.com>
Subject: Re: [PATCH] net/bonding: rename bonded to bonding
Date: Fri, 2 Jun 2023 18:04:48 +0100	[thread overview]
Message-ID: <93f6ea5e-1890-f0e5-717d-12241c8a8fa5@amd.com> (raw)
In-Reply-To: <20230524071204.2484248-1-chaoyong.he@corigine.com>

On 5/24/2023 8:12 AM, Chaoyong He wrote:
> diff --git a/lib/ethdev/rte_ethdev.h b/lib/ethdev/rte_ethdev.h
> index 85439e3a41..e717079dd0 100644
> --- a/lib/ethdev/rte_ethdev.h
> +++ b/lib/ethdev/rte_ethdev.h
> @@ -2036,12 +2036,13 @@ struct rte_eth_dev_owner {
>  /** Device supports link state interrupt */
>  #define RTE_ETH_DEV_INTR_LSC              RTE_BIT32(1)
>  /** Device is a bonded member */
> -#define RTE_ETH_DEV_BONDED_MEMBER          RTE_BIT32(2)
> +#define RTE_ETH_DEV_BONDING_MEMBER          RTE_BIT32(2)
>  #define RTE_ETH_DEV_BONDED_SLAVE                         \
>

Since this is macro in public header, it needs deprecation notice to
rename it, need to send a deprecation notice a release for this release.

Or it is possible to add an alias to existing macro and keep both.


  parent reply	other threads:[~2023-06-02 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  7:12 Chaoyong He
2023-05-24 14:48 ` Stephen Hemminger
2023-06-02 15:15 ` Ferruh Yigit
2023-06-02 17:04 ` Ferruh Yigit [this message]
2023-09-21  6:10 ` [PATCH v2] " Chaoyong He
2023-09-21 10:11   ` 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=93f6ea5e-1890-f0e5-717d-12241c8a8fa5@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=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).