From: Kevin Traynor <ktraynor@redhat.com>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, stable@dpdk.org
Cc: thomas@monjalon.net, Dekel Peled <dekelp@mellanox.com>,
Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Subject: Re: [dpdk-stable] [PATCH] [18.11] net/mlx5: fix match on empty VLAN item in DV mode
Date: Tue, 8 Dec 2020 10:51:06 +0000 [thread overview]
Message-ID: <9b88e5ac-17d9-f940-ea62-4274267a50e1@redhat.com> (raw)
In-Reply-To: <1607419434-16261-1-git-send-email-viacheslavo@nvidia.com>
On 08/12/2020 09:23, Viacheslav Ovsiienko wrote:
> From: Dekel Peled <dekelp@mellanox.com>
>
> From: Dekel Peled <dekelp@mellanox.com>
>
Removed duplicate From: ^ as it was embedding in commit msg.
Please add upstream commit info for backports. For this one I added
[ upstream commit 92818d839e8eb0ce479db826f00aa6d62384fc92 ]
> 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 contradict the flow API specification.
>
> 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.
>
> Fixes: 3d79e4f2d563 ("net/mlx5: fix VLAN match for DV mode")
>
Changed to fixed commit on main branch
Fixes: 00f75a40576b ("net/mlx5: fix VLAN match for DV mode")
If it's a backport where the main branch commit fixes something on main,
then we keep that Fixes: tag. If is fixing an LTS only issue then can
use the LTS branch commit id in the Fixes:.
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> ---> doc/guides/nics/mlx5.rst | 24 +++++++++++++
> drivers/net/mlx5/mlx5_flow_dv.c | 74 ++++++++++++++++++++++++++++++++++++-----
> 2 files changed, 90 insertions(+), 8 deletions(-)
>
Applied, thanks.
prev parent reply other threads:[~2020-12-08 10:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 9:23 Viacheslav Ovsiienko
2020-12-08 10:51 ` Kevin Traynor [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=9b88e5ac-17d9-f940-ea62-4274267a50e1@redhat.com \
--to=ktraynor@redhat.com \
--cc=dekelp@mellanox.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=viacheslavo@mellanox.com \
--cc=viacheslavo@nvidia.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).