From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: dev@dpdk.org, stable@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] app/testpmd: fix copy of raw flow item (revisited)
Date: Mon, 21 May 2018 13:44:34 +0100 [thread overview]
Message-ID: <3748de88-4fe5-c505-e4ef-9c4484be1ea2@intel.com> (raw)
In-Reply-To: <20180521114345.690-1-adrien.mazarguil@6wind.com>
On 5/21/2018 12:44 PM, Adrien Mazarguil wrote:
> While previous fix with the same title does address the main issue, root
> cause is that proper handling of spec/last/mask was overlooked in the
> original patch.
>
> Mask and last fields must be taken into account at all times.
>
> Fixes: d0ad8648b1c5 ("app/testpmd: fix RSS flow action configuration")
> Fixes: 67af7ecc52ec ("app/testpmd: fix copy of raw flow item")
> Cc: stable@dpdk.org
> Cc: Qi Zhang <qi.z.zhang@intel.com>
>
> Signed-off-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-05-21 12:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 15:41 [dpdk-dev] [PATCH " Adrien Mazarguil
2018-05-16 15:41 ` [dpdk-dev] [PATCH 2/2] ethdev: fix shallow copy of flow API RAW item Adrien Mazarguil
2018-05-18 17:06 ` Ferruh Yigit
2018-05-19 14:25 ` Thomas Monjalon
2018-05-21 8:24 ` Adrien Mazarguil
2018-05-21 10:44 ` Ferruh Yigit
2018-05-21 11:18 ` Adrien Mazarguil
2018-05-17 14:44 ` [dpdk-dev] [PATCH 1/2] app/testpmd: fix copy of raw flow item (revisited) Iremonger, Bernard
2018-05-21 11:44 ` [dpdk-dev] [PATCH v2 " Adrien Mazarguil
2018-05-21 11:44 ` [dpdk-dev] [PATCH v2 2/2] ethdev: fix shallow copy of flow API RAW item Adrien Mazarguil
2018-05-21 12:44 ` 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=3748de88-4fe5-c505-e4ef-9c4484be1ea2@intel.com \
--to=ferruh.yigit@intel.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
/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).