From: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Shahaf Shuler <shahafs@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix creation of drop flows
Date: Thu, 15 Jun 2017 14:50:10 +0200 [thread overview]
Message-ID: <20170615125010.GT18438@autoinstall.dev.6wind.com> (raw)
In-Reply-To: <f8f6fc39-f2a5-5768-02b9-f39e0689324e@intel.com>
On Thu, Jun 15, 2017 at 01:34:31PM +0100, Ferruh Yigit wrote:
> On 6/15/2017 9:25 AM, Nelio Laranjeiro wrote:
> > Drop flows being created when the port is stop should not access to the drop
> > table hash queues as it is invalid.
> >
> > Fixes: 028761059aeb ("net/mlx5: use an RSS drop queue")
> >
> > Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
> > Acked-by: Shahaf Shuler <shahafs@mellanox.com>
>
> Applied to dpdk-next-net/master, thanks.
>
> This required solving merge conflict, although it looks simple, can you
> please confirm the final commit.
it is good for me.
Thanks Ferruh,
--
Nélio Laranjeiro
6WIND
prev parent reply other threads:[~2017-06-15 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 8:25 Nelio Laranjeiro
2017-06-15 12:34 ` Ferruh Yigit
2017-06-15 12:50 ` Nélio Laranjeiro [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=20170615125010.GT18438@autoinstall.dev.6wind.com \
--to=nelio.laranjeiro@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=shahafs@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).