From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dekel Peled <dekelp@mellanox.com>,
matan@mellanox.com, viacheslavo@mellanox.com,
rasland@mellanox.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/mlx5: fix match on empty VLAN item in DV mode
Date: Mon, 11 May 2020 18:19:12 +0100 [thread overview]
Message-ID: <6310eecb-32a5-953e-f798-c931732fa006@intel.com> (raw)
In-Reply-To: <851d6f105d060c15334220049b0e311ceeb774b2.1588683371.git.dekelp@mellanox.com>
On 5/5/2020 1:57 PM, Dekel Peled wrote:
> In existing implementation, using wild card VLAN item is not allowed.
> A VLAN item in flow pattern must include VLAN ID (vid) value.
> This obligation contradics the intention of documentation update [1].
At this perspective it is not "documentation update" but "flow API spec/contract".
>
> This patch updates the VLAN item validation and translation, to allow
> wild card VLAN item, without VLAN ID value.
> User guide and release notes are updated accordingly.
>
> [1] http://patches.dpdk.org/patch/69207/
Can you please refer to the commit in the repo, instead of a superseded patch in
patchwork?
Will update above while merging.
>
> Fixes: 00f75a40576b ("net/mlx5: fix VLAN match for DV mode")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
<...>
next prev parent reply other threads:[~2020-05-11 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 12:57 [dpdk-dev] " Dekel Peled
2020-05-10 10:48 ` Raslan Darawsheh
2020-05-11 17:19 ` Ferruh Yigit [this message]
2020-05-11 18:19 ` [dpdk-dev] [dpdk-stable] " Dekel Peled
2020-05-11 20:29 ` Ferruh Yigit
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=6310eecb-32a5-953e-f798-c931732fa006@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dekelp@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=rasland@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@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).