patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Suanming Mou <suanmingm@mellanox.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 19.11 00/11] net/mlx5: fix patch backport
Date: Fri, 28 Feb 2020 11:17:39 +0000	[thread overview]
Message-ID: <bf1e33e592190ec3526dd82d55a310640e5c001e.camel@debian.org> (raw)
In-Reply-To: <1582860835-282594-1-git-send-email-suanmingm@mellanox.com>

On Fri, 2020-02-28 at 11:33 +0800, Suanming Mou wrote:
> Please remove the commit below with rebase first:
> dec473d net/mlx5: fix metadata split with encap action
> 
> The commit makes the wrong patch order.
> Remove the commit will not cause any conflicts.
> 
> Dekel Peled (2):
>   net/mlx5: unify validation of drop action
>   net/mlx5: update description of validation functions
> 
> Matan Azrad (2):
>   net/mlx5: fix encap/decap validation
>   net/mlx5: fix metadata split with encap action
> 
> Suanming Mou (7):
>   net/mlx5: support maximum flow id allocation
>   net/mlx5: fix register usage in meter
>   net/mlx5: fix layer validation with decapsulation
>   net/mlx5: fix layer type in header modify action
>   net/mlx5: fix layer flags missing in metadata
>   net/mlx5: fix match information in meter
>   net/mlx5: fix VLAN actions in meter
> 
>  drivers/net/mlx5/mlx5.c            |  19 +-
>  drivers/net/mlx5/mlx5.h            |   4 +
>  drivers/net/mlx5/mlx5_devx_cmds.c  |   2 +
>  drivers/net/mlx5/mlx5_flow.c       | 366 ++++++++++++++++-----------
> -
>  drivers/net/mlx5/mlx5_flow.h       |  40 ++-
>  drivers/net/mlx5/mlx5_flow_dv.c    | 485 +++++++++++++++++++++----
> ------------
>  drivers/net/mlx5/mlx5_flow_verbs.c |  12 +
>  drivers/net/mlx5/mlx5_prm.h        |   7 +-
>  8 files changed, 552 insertions(+), 383 deletions(-)

Thank you, applied. I also dropped the previous version of "net/mlx5:
fix metadata split with encap action" in favour of yours.

-- 
Kind regards,
Luca Boccassi

      parent reply	other threads:[~2020-02-28 11:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  3:33 Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 01/11] net/mlx5: unify validation of drop action Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 02/11] net/mlx5: update description of validation functions Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 03/11] net/mlx5: support maximum flow id allocation Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 04/11] net/mlx5: fix register usage in meter Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 05/11] net/mlx5: fix encap/decap validation Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 06/11] net/mlx5: fix layer validation with decapsulation Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 07/11] net/mlx5: fix layer type in header modify action Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 08/11] net/mlx5: fix layer flags missing in metadata Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 09/11] net/mlx5: fix match information in meter Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 10/11] net/mlx5: fix VLAN actions " Suanming Mou
2020-02-28  3:33 ` [dpdk-stable] [PATCH 19.11 11/11] net/mlx5: fix metadata split with encap action Suanming Mou
2020-02-28 11:17 ` Luca Boccassi [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=bf1e33e592190ec3526dd82d55a310640e5c001e.camel@debian.org \
    --to=bluca@debian.org \
    --cc=stable@dpdk.org \
    --cc=suanmingm@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).