From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: Jerin Jacob <jerinjacobk@gmail.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Shahaf Shuler <shahafs@mellanox.com>,
David Marchand <david.marchand@redhat.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Stephen Hemminger <stephen@networkplumber.org>,
John Daley <johndale@cisco.com>,
"Wei Hu (Xavier" <xavier.huwei@huawei.com>,
Ziyang Xuan <xuanziyang2@huawei.com>,
"Zhao1, Wei" <wei.zhao1@intel.com>,
Rasesh Mody <rmody@marvell.com>,
Andrew Rybchenko <arybchenko@solarflare.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce removal of ethdev flow director API
Date: Thu, 06 Aug 2020 02:30:59 +0200 [thread overview]
Message-ID: <8793975.PtsIUokAhJ@thomas> (raw)
In-Reply-To: <0c1ee8b2-0ceb-6b6b-c0db-056166465323@solarflare.com>
> >>> The flow director config, part of the legacy filtering API,
> >>> was marked as deprecated last year.
> >>> A separate notice is added to make clear that these specific structs
> >>> will be removed as well in DPDK 20.11, as the rest of the legacy
> >>> filtering API.
> >>>
> >>> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> >> Acked-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> > Acked-by: Jerin Jacob <jerinj@marvell.com>
> Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Acked-by: David Marchand <david.marchand@redhat.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied
next prev parent reply other threads:[~2020-08-06 0:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 17:49 [dpdk-dev] [PATCH] doc: announce removal of ethdev flow director API Thomas Monjalon
2020-08-03 17:57 ` Ajit Khaparde
2020-08-04 3:51 ` Jerin Jacob
2020-08-05 13:46 ` Andrew Rybchenko
2020-08-06 0:30 ` Thomas Monjalon [this message]
2020-08-04 7:36 ` David Marchand
2020-08-04 7:49 ` Hemant Agrawal
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=8793975.PtsIUokAhJ@thomas \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=johndale@cisco.com \
--cc=rmody@marvell.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=wei.zhao1@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=xuanziyang2@huawei.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 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.