From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>,
"jerinj@marvell.com" <jerinj@marvell.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 7/01/2021
Date: Thu, 7 Jan 2021 18:07:29 +0000 [thread overview]
Message-ID: <ebb4bad1-bf36-8c75-d0bb-a5b5c1f17245@intel.com> (raw)
In-Reply-To: <48586cca-1911-8497-4692-4b331d895045@intel.com>
On 1/7/2021 6:04 PM, Ferruh Yigit wrote:
> Meeting minutes of 7 January 2021
> ---------------------------------
<...>
> * rte_flow action change RFC is out, it is a design change, please review
> * http://patchwork.dpdk.org/patch/85384/
Hi Andrew, Jerin, Ajit, Qi,
Can you please help on reviewing the above rte_flow patch, as far as I
understand from Thomas it may have a long term affect for all drivers.
Thanks,
ferruh
prev parent reply other threads:[~2021-01-07 18:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 18:04 Ferruh Yigit
2021-01-07 18:07 ` Ferruh Yigit [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=ebb4bad1-bf36-8c75-d0bb-a5b5c1f17245@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=qi.z.zhang@intel.com \
--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).