DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jack Min <jackmin@mellanox.com>
To: Dekel Peled <dekelp@mellanox.com>
Cc: Yongseok Koh <yskoh@mellanox.com>,
	Slava Ovsiienko <viacheslavo@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Ori Kam <orika@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix define of added tunnel layer bit
Date: Fri, 19 Jul 2019 02:58:32 +0000	[thread overview]
Message-ID: <20190719025823.dhmu43vchriz3vta@mellanox.com> (raw)
In-Reply-To: <70e5550c339eb720592d2b364069f74f232137a3.1563478168.git.dekelp@mellanox.com>

On Thu, 19-07-18, 22:41, Dekel Peled wrote:
> The new define MLX5_FLOW_LAYER_IPIP is using the same value as
> existing define MLX5_FLOW_LAYER_GRE_KEY.
> This patch updates the values to be in order.
> 
> Fixes: 1b5624cd9062 ("net/mlx5: support IP-in-IP tunnel")
> Signed-off-by: Dekel Peled <dekelp@mellanox.com>
> ---
>  drivers/net/mlx5/mlx5_flow.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_flow.h b/drivers/net/mlx5/mlx5_flow.h
> index ece967a..3f96bec 100644
> --- a/drivers/net/mlx5/mlx5_flow.h
> +++ b/drivers/net/mlx5/mlx5_flow.h
> @@ -58,8 +58,8 @@
>  #define MLX5_FLOW_LAYER_ICMP6 (1u << 19)
>  #define MLX5_FLOW_LAYER_GRE_KEY (1u << 20)
>  
> -#define MLX5_FLOW_LAYER_IPIP (1u << 20)
> -#define MLX5_FLOW_LAYER_IPV6_ENCAP (1u << 21)
> +#define MLX5_FLOW_LAYER_IPIP (1u << 21)
> +#define MLX5_FLOW_LAYER_IPV6_ENCAP (1u << 22)
>  
>  /* Outer Masks. */
>  #define MLX5_FLOW_LAYER_OUTER_L3 \
> -- 
> 1.8.3.1
> 
Acked-by: Xiaoyu Min <jackmin@mellanox.com>

  reply	other threads:[~2019-07-19  2:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-18 19:41 Dekel Peled
2019-07-19  2:58 ` Jack Min [this message]
2019-07-19  4:28 ` Slava Ovsiienko
2019-07-21  7:51 ` Raslan Darawsheh

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=20190719025823.dhmu43vchriz3vta@mellanox.com \
    --to=jackmin@mellanox.com \
    --cc=dekelp@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=orika@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=viacheslavo@mellanox.com \
    --cc=yskoh@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).