DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	John McNamara <john.mcnamara@intel.com>,
	Marko Kovacevic <marko.kovacevic@intel.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	John Daley <johndale@cisco.com>,
	Hyong Youb Kim <hyonkim@cisco.com>,
	Beilei Xing <beilei.xing@intel.com>,
	Qi Zhang <qi.z.zhang@intel.com>,
	Wenzhuo Lu <wenzhuo.lu@intel.com>, Rosen Xu <rosen.xu@intel.com>,
	Konstantin Ananyev <konstantin.ananyev@intel.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Yongseok Koh <yskoh@mellanox.com>,
	Viacheslav Ovsiienko <viacheslavo@mellanox.com>,
	Rasesh Mody <rmody@marvell.com>,
	Shahed Shaikh <shshaikh@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: remove deprecated ethdev features
Date: Tue, 06 Aug 2019 23:42:52 +0200	[thread overview]
Message-ID: <3306050.VdHAyG8KI6@xps> (raw)
In-Reply-To: <CACZ4nhubp5QgFaJ0EYqOLwDVwkVy4gciMnG+E9t7kC=9DvLQMQ@mail.gmail.com>

> > > > As legacy filter API "filter_ctrl" is superseded since 2017 by the
> > > > rte_flow API, and got the deprecated attribute in DPDK 19.05, it is
> > > > time to remove the associated features from the matrix.
> > > > Not documenting deprecated features as supported will avoid confusion.
> > > >
> > > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > > Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>

Applied




  reply	other threads:[~2019-08-06 21:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 15:57 Thomas Monjalon
2019-07-31  9:34 ` Andrew Rybchenko
2019-07-31 10:35   ` Jerin Jacob Kollanukkaran
2019-07-31 10:47     ` Ajit Khaparde
2019-08-06 21:42       ` Thomas Monjalon [this message]
2019-07-31  9:45 ` David Marchand
2019-07-31 13:00   ` Thomas Monjalon
2019-10-15 11:08 ` Yigit, Ferruh
2019-10-15 12:31   ` Andrew Rybchenko
2019-10-15 12:58     ` Ferruh Yigit
2019-10-15 14:16       ` Jerin Jacob
2019-10-15 15:55         ` Ferruh Yigit
2019-10-15 16:19           ` Jerin Jacob
2019-10-15 20:00             ` Ajit Khaparde
2019-10-16 10:02             ` Ferruh Yigit
2019-10-16 10:08               ` Jerin Jacob
2019-10-16 10:16                 ` Ferruh Yigit
2019-10-16 10:20                   ` Jerin Jacob
2019-10-25 12:28                     ` 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=3306050.VdHAyG8KI6@xps \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=arybchenko@solarflare.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=hyonkim@cisco.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=johndale@cisco.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=rmody@marvell.com \
    --cc=rosen.xu@intel.com \
    --cc=shahafs@mellanox.com \
    --cc=shshaikh@marvell.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=viacheslavo@mellanox.com \
    --cc=wenzhuo.lu@intel.com \
    --cc=yskoh@mellanox.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).