From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix TPID check for VLAN push action on E-Switch
Date: Thu, 22 Nov 2018 12:08:47 +0000 [thread overview]
Message-ID: <DB7PR05MB4426FDB7B4F92953172A1203C3DB0@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1542799669-21425-1-git-send-email-viacheslavo@mellanox.com>
Wednesday, November 21, 2018 1:28 PM, Viacheslav Ovsiienko:
> Subject: [PATCH] net/mlx5: fix TPID check for VLAN push action on E-Switch
>
> The VLAN push action on E-Switch supports only 802.1Q (0x8100) and
> 802.1AD (0x88A8) Tag Protocol ID (TPID) insertions. The parameter check for
> RTE_FLOW_ACTION_TYPE_OF_PUSH_VLAN action is added.
>
> Fixes: 57123c00c1b8 ("net/mlx5: add Linux TC flower driver for E-Switch
> flow")
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Applied to next-net-mlx, thanks.
prev parent reply other threads:[~2018-11-22 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 11:27 Viacheslav Ovsiienko
2018-11-22 12:08 ` Shahaf Shuler [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=DB7PR05MB4426FDB7B4F92953172A1203C3DB0@DB7PR05MB4426.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@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).