From: Gregory Etelson <getelson@nvidia.com>
To: NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
Ori Kam <orika@nvidia.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Bernard Iremonger <bernard.iremonger@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>, Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
Jeff Guo <jia.guo@intel.com>, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] app/testpmd: fix flow rules list after port stop
Date: Tue, 17 Nov 2020 19:08:38 +0000 [thread overview]
Message-ID: <MN2PR12MB46394ACBFBC1EF2C2A1A6E38A5E20@MN2PR12MB4639.namprd12.prod.outlook.com> (raw)
In-Reply-To: <4471739.bWhk7Xqv4u@thomas>
Hello,
> 13/09/2020 14:12, Ori Kam:
> > Hi Ferruh,
> > Can we proceed with this patch?
>
> Below, you said "first thing to do it update the rte_flow doc".
> So I am expecting a patch on the doc to start this discussion.
> This testpmd patch is on hold in my understanding.
>
Documentation patch "doc: flow rule removal on port stop"
Was sent to the list on September 16. The patch URL is
https://inbox.dpdk.org/dev/20200916111854.1949-1-getelson@nvidia.com/#r
next prev parent reply other threads:[~2020-11-17 19:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200810161523.6904-1-getelson@mellanox.com>
2020-08-20 8:40 ` Gregory Etelson
2020-08-25 15:51 ` Ferruh Yigit
2020-08-26 17:34 ` Ori Kam
2020-09-13 12:12 ` Ori Kam
2020-09-13 14:00 ` Thomas Monjalon
2020-11-17 19:08 ` Gregory Etelson [this message]
2020-08-11 6:14 Gregory Etelson
2020-11-24 14:42 ` Ajit Khaparde
2020-11-26 15:41 ` 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=MN2PR12MB46394ACBFBC1EF2C2A1A6E38A5E20@MN2PR12MB4639.namprd12.prod.outlook.com \
--to=getelson@nvidia.com \
--cc=beilei.xing@intel.com \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jia.guo@intel.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--cc=wenzhuo.lu@intel.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).