All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Chenbo Xia <chenbo.xia@intel.com>, Rosen Xu <rosen.xu@intel.com>,
	<dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: mark old macros as deprecated
Date: Wed, 3 Nov 2021 09:00:38 +0000	[thread overview]
Message-ID: <6a69d4fc-3f69-799a-e273-c45c3bbcb04c@intel.com> (raw)
In-Reply-To: <20211102170535.1e2ce414@hermes.local>

On 11/3/2021 12:05 AM, Stephen Hemminger wrote:
> On Tue,  2 Nov 2021 23:44:34 +0000
> Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> 
>> 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>
>> ---
>> Cc: Stephen Hemminger <stephen@networkplumber.org>
>> ---
>>   lib/ethdev/rte_ethdev.h | 474 +++++++++++++++++++++-------------------
>>   1 file changed, 244 insertions(+), 230 deletions(-)
>>
> 
> I assume all of current tree compiles cleanly.

Yes.

> Should there be a release note?
> 

Ack, I will add in v2.

> Acked-by: Stephen Hemminger <stephen@networkplumber.org>
> 


  reply	other threads:[~2021-11-03  9:00 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 [this message]
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
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=6a69d4fc-3f69-799a-e273-c45c3bbcb04c@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=rosen.xu@intel.com \
    --cc=somnath.kotur@broadcom.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.