From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [PATCH 1/2] net/mlx5: fix flow queues array allocation
Date: Thu, 13 Apr 2017 12:00:50 +0100 [thread overview]
Message-ID: <a9bc4e5b-adcb-367c-353a-d43bb9e9865a@intel.com> (raw)
In-Reply-To: <79629f2f-9518-df31-2704-756269ae1205@intel.com>
On 4/12/2017 5:51 PM, Ferruh Yigit wrote:
> On 4/12/2017 4:02 PM, Ferruh Yigit wrote:
>> On 4/11/2017 4:21 PM, Nelio Laranjeiro wrote:
>>> Flow queues array offset is not properly computed causing all sorts of
>>> issues. Address it by making the rte_flow structure less complex.
>>>
>>> Fixes: 360663e1df46 ("net/mlx5: prepare support for RSS action rule")
>>>
>>> Signed-off-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
>>> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
>>
>> Series applied to dpdk-next-net/master, thanks.
>
> Removed from tree, and patchwork status updated to "New", please check
> comment about rte_panic() usage in patch 2/2.
Series applied _back_ to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-04-13 11:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 15:21 [PATCH 1/2] net/mlx5: fix flow queues array allocation Nelio Laranjeiro
2017-04-11 15:21 ` [PATCH 2/2] net/mlx5: panic when destroying a queue in use Nelio Laranjeiro
2017-04-12 16:48 ` Ferruh Yigit
2017-04-12 17:04 ` Adrien Mazarguil
2017-04-12 15:02 ` [PATCH 1/2] net/mlx5: fix flow queues array allocation Ferruh Yigit
2017-04-12 16:51 ` Ferruh Yigit
2017-04-13 11:00 ` 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=a9bc4e5b-adcb-367c-353a-d43bb9e9865a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.