From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Cc: dev@dpdk.org, Yongseok Koh <yskoh@mellanox.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] net/mlx5: fix flow application order on stop/start
Date: Tue, 30 May 2017 13:33:20 +0100 [thread overview]
Message-ID: <3aa12a49-01f1-62f8-fb9a-39d93695df30@intel.com> (raw)
In-Reply-To: <20170529132909.GQ1758@6wind.com>
On 5/29/2017 2:29 PM, Adrien Mazarguil wrote:
> On Mon, May 29, 2017 at 11:40:58AM +0200, Nelio Laranjeiro wrote:
>> Flow rules must be applied in the same order as they have been created and
>> thus destroyed in the reverse order.
>>
>> Fixes: 2097d0d1e2cc ("net/mlx5: support basic flow items and actions")
>>
>> Cc: stable@dpdk.org
>> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>> Acked-by: Yongseok Koh <yskoh@mellanox.com>
>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-05-30 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 9:40 Nelio Laranjeiro
2017-05-29 13:29 ` Adrien Mazarguil
2017-05-30 12:33 ` 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=3aa12a49-01f1-62f8-fb9a-39d93695df30@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.org \
--cc=yskoh@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).