All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>, dev@dpdk.org
Cc: Yongseok Koh <yskoh@mellanox.com>,
	Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [PATCH 0/5] net/mlx5: fixes
Date: Wed, 1 Nov 2017 14:34:41 -0700	[thread overview]
Message-ID: <86ee2438-c769-a741-358f-cd8ceb489504@intel.com> (raw)
In-Reply-To: <cover.1509464921.git.nelio.laranjeiro@6wind.com>

On 10/31/2017 8:51 AM, Nelio Laranjeiro wrote:
> - Multiple fixes for tunnels in flow actions.
> - fix some mistakes in flow director code.
> 
> Nelio Laranjeiro (5):
>   net/mlx5: fix parser inner value
>   net/mlx5: fix flows when VXLAN tunnel is 0
>   net/mlx5: fix RSS tunneled flow without outer
>   net/mlx5: fix fdir flow removal
>   net/mlx5: fix flow director TCPv6 filter

Series applied to dpdk-next-net/master, thanks.


Except patch 3/5, it squashed into relevant commit [1].

[1]: "net/mlx5: fix RSS action for tunneled packets"

      parent reply	other threads:[~2017-11-01 21:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-31 15:51 [PATCH 0/5] net/mlx5: fixes Nelio Laranjeiro
2017-10-31 15:51 ` [PATCH 1/5] net/mlx5: fix parser inner value Nelio Laranjeiro
2017-10-31 23:46   ` Yongseok Koh
2017-10-31 15:51 ` [PATCH 2/5] net/mlx5: fix flows when VXLAN tunnel is 0 Nelio Laranjeiro
2017-11-01 18:56   ` Yongseok Koh
2017-10-31 15:51 ` [PATCH 3/5] net/mlx5: fix RSS tunneled flow without outer Nelio Laranjeiro
2017-11-01 18:56   ` Yongseok Koh
2017-10-31 15:51 ` [PATCH 4/5] net/mlx5: fix fdir flow removal Nelio Laranjeiro
2017-11-01  0:43   ` Yongseok Koh
2017-10-31 15:51 ` [PATCH 5/5] net/mlx5: fix flow director TCPv6 filter Nelio Laranjeiro
2017-11-01  0:43   ` Yongseok Koh
2017-11-01 21:34 ` 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=86ee2438-c769-a741-358f-cd8ceb489504@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.org \
    --cc=nelio.laranjeiro@6wind.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.