From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ori Kam <orika@mellanox.com>, Dekel Peled <dekelp@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] examples/flow_filtering: fix example documentation
Date: Tue, 8 Jan 2019 15:05:13 +0000 [thread overview]
Message-ID: <06c16bb2-e60a-ca13-468c-8a0bf7e002c6@intel.com> (raw)
In-Reply-To: <AM4PR05MB342502B8E7561EED206B58C0DBB40@AM4PR05MB3425.eurprd05.prod.outlook.com>
On 12/25/2018 9:54 AM, Ori Kam wrote:
>
>
>> -----Original Message-----
>> From: dev <dev-bounces@dpdk.org> On Behalf Of Dekel Peled
>> Sent: Tuesday, December 25, 2018 9:42 AM
>> To: Ori Kam <orika@mellanox.com>
>> Cc: dev@dpdk.org; Dekel Peled <dekelp@mellanox.com>
>> Subject: [dpdk-dev] [PATCH v2] examples/flow_filtering: fix example
>> documentation
>>
>> Previous patch removed the VLAN item from example code.
>> This patch fixes the code and documentation accordingly.
>>
>> Code update includes fix of comments, and removal of redundant
>> variables and their initialization.
>> Documentation update reflects the code changes done in previous
>> patch and in this patch.
>>
>> Fixes: 9af4eb565710 ("examples/flow_filtering: remove VLAN item")
>> Cc: orika@mellanox.com
>>
>> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
>
> Acked-by: Ori Kam <orika@mellanox.com>
>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-01-08 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 10:50 [dpdk-dev] [PATCH] " Dekel Peled
2018-12-25 3:25 ` Ori Kam
2018-12-25 6:30 ` Dekel Peled
2018-12-25 6:37 ` Ori Kam
2019-01-02 14:52 ` Ferruh Yigit
2019-01-03 7:40 ` Ori Kam
2018-12-25 7:42 ` [dpdk-dev] [PATCH v2] " Dekel Peled
2018-12-25 9:54 ` Ori Kam
2019-01-08 15:05 ` 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=06c16bb2-e60a-ca13-468c-8a0bf7e002c6@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=orika@mellanox.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).