DPDK patches and discussions
 help / color / mirror / Atom feed
From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>,
	dev@dpdk.org
Subject: Re: [PATCH 00/10] ethdev: cleanup deprecated defines
Date: Fri, 5 Aug 2022 11:01:09 +0300	[thread overview]
Message-ID: <15fc2ac6-29ce-35e2-417b-6332caf0d6ec@oktetlabs.ru> (raw)
In-Reply-To: <20220804122912.484c8a79@hermes.local>

On 8/4/22 22:29, Stephen Hemminger wrote:
> On Thu,  4 Aug 2022 22:05:52 +0300
> Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru> wrote:
> 
>> Remove deprecated because of invalid namespace defines.
>>
>> Andrew Rybchenko (10):
>>    ethdev: remove deprecated link speed and duplex defines
>>    ethdev: remove deprecated Rx and Tx multi-queue mode defines
>>    ethdev: remove deprecated defines for RSS configuration
>>    ethdev: remove deprecated Rx and Tx offload defines
>>    ethdev: remove deprecated DCB and VMDq defines
>>    ethdev: remove deprecated tunnel type defines
>>    ethdev: remove deprecated flow control defines
>>    ethdev: remove deprecated VLAN offload configuration defines
>>    ethdev: remove deprecated maximum Rx MAC addresses define
>>    ethdev: remove deprecated metadata dynamic fields defines
>>
>>   doc/guides/rel_notes/release_22_11.rst |  34 ++++
>>   lib/ethdev/rte_ethdev.h                | 242 -------------------------
>>   lib/ethdev/rte_flow.h                  |   4 -
>>   3 files changed, 34 insertions(+), 246 deletions(-)
>>
> 
> 
> Looks good. I assume the flow director (FDIR) defines should also
> go away in this release when it is removed.

Yes, I wanted but simply forgot to mention it in the cover letter.
FDIR defines are covered by fdir cleanup patch series [1].
I decided that it does not deserve separate patch.

[1] 
https://patches.dpdk.org/project/dpdk/patch/20220803111358.375544-4-andrew.rybchenko@oktetlabs.ru/

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

Thanks for the review, Stephen.

  reply	other threads:[~2022-08-05  8:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04 19:05 Andrew Rybchenko
2022-08-04 19:05 ` [PATCH 01/10] ethdev: remove deprecated link speed and duplex defines Andrew Rybchenko
2022-08-04 19:05 ` [PATCH 02/10] ethdev: remove deprecated Rx and Tx multi-queue mode defines Andrew Rybchenko
2022-08-04 19:05 ` [PATCH 03/10] ethdev: remove deprecated defines for RSS configuration Andrew Rybchenko
2022-08-23  8:41   ` David Marchand
2022-08-23 18:08     ` Ferruh Yigit
2022-08-04 19:05 ` [PATCH 04/10] ethdev: remove deprecated Rx and Tx offload defines Andrew Rybchenko
2022-08-04 19:05 ` [PATCH 05/10] ethdev: remove deprecated DCB and VMDq defines Andrew Rybchenko
2022-08-23  8:41   ` David Marchand
2022-08-23 18:08     ` Ferruh Yigit
2022-08-04 19:05 ` [PATCH 06/10] ethdev: remove deprecated tunnel type defines Andrew Rybchenko
2022-08-23  8:41   ` David Marchand
2022-08-04 19:05 ` [PATCH 07/10] ethdev: remove deprecated flow control defines Andrew Rybchenko
2022-08-04 19:06 ` [PATCH 08/10] ethdev: remove deprecated VLAN offload configuration defines Andrew Rybchenko
2022-08-04 19:06 ` [PATCH 09/10] ethdev: remove deprecated maximum Rx MAC addresses define Andrew Rybchenko
2022-08-04 19:06 ` [PATCH 10/10] ethdev: remove deprecated metadata dynamic fields defines Andrew Rybchenko
2022-08-04 19:29 ` [PATCH 00/10] ethdev: cleanup deprecated defines Stephen Hemminger
2022-08-05  8:01   ` Andrew Rybchenko [this message]
2022-08-23  8:41 ` David Marchand
2022-08-23 18:08   ` Ferruh Yigit
2022-08-24  6:46     ` David Marchand
2022-08-24  7:51       ` 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=15fc2ac6-29ce-35e2-417b-6332caf0d6ec@oktetlabs.ru \
    --to=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@xilinx.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 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).