From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: David Marchand <david.marchand@redhat.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev <dev@dpdk.org>, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
John Daley <johndale@cisco.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
Ziyang Xuan <xuanziyang2@huawei.com>,
Wei Zhao <wei.zhao1@intel.com>, Rasesh Mody <rmody@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce removal of ethdev flow director API
Date: Tue, 4 Aug 2020 07:49:09 +0000 [thread overview]
Message-ID: <DB7PR04MB4459BD28F536B1E1399D2CE4894A0@DB7PR04MB4459.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8yXkOEF=24nqWSkm0zR2Ux=CqMRFuNYu6GT5d+jBbTroQ@mail.gmail.com>
> On Mon, Aug 3, 2020 at 7:49 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> >
> > 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: David Marchand <david.marchand@redhat.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
prev parent reply other threads:[~2020-08-04 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 17:49 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
2020-08-04 7:36 ` David Marchand
2020-08-04 7:49 ` Hemant Agrawal [this message]
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=DB7PR04MB4459BD28F536B1E1399D2CE4894A0@DB7PR04MB4459.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--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=jerinj@marvell.com \
--cc=johndale@cisco.com \
--cc=rmody@marvell.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--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 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).