From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Asaf Penso <asafp@nvidia.com>, Ori Kam <orika@nvidia.com>,
Jack Min <jackmin@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: more info of rte flow shared action
Date: Wed, 3 Feb 2021 11:58:31 +0000 [thread overview]
Message-ID: <cdf98db2-bc44-17c1-5509-712ad587617d@intel.com> (raw)
In-Reply-To: <DM5PR12MB2406AF999A7385F744E96500CDB49@DM5PR12MB2406.namprd12.prod.outlook.com>
On 2/3/2021 9:02 AM, Asaf Penso wrote:
> Hi Jack,
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Ori Kam
>> Sent: Wednesday, February 3, 2021 9:51 AM
>> To: Jack Min <jackmin@nvidia.com>
>> Cc: dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH 1/2] doc: more info of rte flow shared action
>>
>> Hi Jack,
>>
>>> -----Original Message-----
>>> From: Jack Min <jackmin@nvidia.com>
>>> Subject: [PATCH 1/2] doc: more info of rte flow shared action
>>>
>>> Added more information of shared action on how to update, query, and
>>> the benefits.
>>>
>>> Signed-off-by: Xiaoyu Min <jackmin@nvidia.com>
>>
>> Acked-by: Ori Kam <orika@nvidia.com>
>> Best,
>> Ori
>
> Reviewed-by: Asaf Penso <asafp@nvidia.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2021-02-03 11:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 12:23 [dpdk-dev] [PATCH 0/2] doc update for " Jack Min
2021-02-02 12:23 ` [dpdk-dev] [PATCH 1/2] doc: more info of " Jack Min
2021-02-03 7:50 ` Ori Kam
2021-02-03 9:02 ` Asaf Penso
2021-02-03 11:58 ` Ferruh Yigit [this message]
2021-02-02 12:23 ` [dpdk-dev] [PATCH 2/2] doc: group mlx5 shared actions Jack Min
2021-02-03 9:02 ` Asaf Penso
2021-02-03 11:59 ` [dpdk-dev] [PATCH 0/2] doc update for rte flow shared action Ferruh Yigit
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=cdf98db2-bc44-17c1-5509-712ad587617d@intel.com \
--to=ferruh.yigit@intel.com \
--cc=asafp@nvidia.com \
--cc=dev@dpdk.org \
--cc=jackmin@nvidia.com \
--cc=orika@nvidia.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).