All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Tyler Retzlaff <roretzla@linux.microsoft.com>,
	Jerin Jacob <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v3] ethdev: mark old macros as deprecated
Date: Fri, 14 Jan 2022 09:01:59 +0000	[thread overview]
Message-ID: <3db08308-e490-8284-4289-6fcec74b7c33@intel.com> (raw)
In-Reply-To: <SN6PR11MB35048C7E73569C11DDC947C19C549@SN6PR11MB3504.namprd11.prod.outlook.com>

On 1/14/2022 6:45 AM, Xia, Chenbo wrote:
>> -----Original Message-----
>> From: Yigit, Ferruh <ferruh.yigit@intel.com>
>> Sent: Wednesday, January 12, 2022 10:36 PM
>> To: Thomas Monjalon <thomas@monjalon.net>; Andrew Rybchenko
>> <andrew.rybchenko@oktetlabs.ru>; Hemant Agrawal <hemant.agrawal@nxp.com>;
>> Tyler Retzlaff <roretzla@linux.microsoft.com>; Xia, Chenbo
>> <chenbo.xia@intel.com>; Jerin Jacob <jerinj@marvell.com>
>> Cc: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>; Stephen Hemminger
>> <stephen@networkplumber.org>
>> Subject: [PATCH v3] ethdev: mark old macros as deprecated
>>
>> Old macros kept for backward compatibility, but this cause old macro
>> usage to sneak in silently.
>>
>> Marking old macros as deprecated. Downside is this will cause some noise
>> for applications that are using old macros.
>>
>> Fixes: 295968d17407 ("ethdev: add namespace")
>>
>> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>> v2:
>> * Release notes updated
>>
>> v3:
>> * Update 22.03 release note
>> ---
>>   doc/guides/rel_notes/release_22_03.rst |   3 +
>>   lib/ethdev/rte_ethdev.h                | 474 +++++++++++++------------
>>   2 files changed, 247 insertions(+), 230 deletions(-)
> 
> Acked-by: Chenbo Xia <chenbo.xia@intel.com>

Applied to dpdk-next-net/main, thanks.

  reply	other threads:[~2022-01-14  9:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29 21:47 [dpdk-dev] [RFC] ethdev: mark old ETH_LINK macros as deprecated Stephen Hemminger
2021-11-01 12:30 ` Ferruh Yigit
2021-11-02 23:44 ` [dpdk-dev] [PATCH] ethdev: mark old " Ferruh Yigit
2021-11-03  0:05   ` Stephen Hemminger
2021-11-03  9:00     ` Ferruh Yigit
2021-11-03 22:48   ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-11-04 11:03     ` Ferruh Yigit
2021-11-04 12:59       ` Thomas Monjalon
2021-11-05 13:40         ` Andrew Rybchenko
2021-11-05 15:05           ` Thomas Monjalon
2021-11-05 16:26             ` Stephen Hemminger
2021-11-05 21:33               ` Ferruh Yigit
2021-11-06  7:46                 ` Thomas Monjalon
2022-01-12 14:36     ` [PATCH v3] " Ferruh Yigit
2022-01-14  6:45       ` Xia, Chenbo
2022-01-14  9:01         ` Ferruh Yigit [this message]
2021-11-04 11:04   ` [dpdk-dev] [PATCH] ethdev: fix crash on owner delete Ferruh Yigit
2021-11-05  3:03     ` [dpdk-dev] [dpdk-stable] " Xia, Chenbo
2021-11-05 13:16       ` Thomas Monjalon
2021-11-05 13:36         ` Andrew Rybchenko
2021-11-05 14:36           ` 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=3db08308-e490-8284-4289-6fcec74b7c33@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=roretzla@linux.microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.