Hi,
> -----Original Message-----
> From: Bing Zhao <bi...@nvidia.com>
> Sent: Friday, June 30, 2023 8:43 AM
> To: Matan Azrad <ma...@nvidia.com>; Slava Ovsiienko
> <viachesl...@nvidia.com>; Ori Kam <or...@nvidia.com>; Suanming Mou
> <suanmi...@nvidia.com>; Raslan Darawsheh <rasl...@nvidia.com>
> Cc: dev@dpdk.org; Michael Baum <michae...@nvidia.com>
> Subject: [PATCH 1/7] net/mlx5: fix the modify field check of tag
>
> The new member "tag_index" was added into the structure
> "rte_flow_action_modify_data". It is the index of the header inside
> encapsulation level. Both the "RTE_FLOW_FIELD_TAG" and
> "MLX5_RTE_FLOW_FIELD_META_REG" types will use this member instead of
> the "level", but the "level" will still be supported for the compatibility.
>
> In the validation stage, not only the "RTE_FLOW_FIELD_TAG" type, but also
> the "MLX5_RTE_FLOW_FIELD_META_REG" needs to be checked.
>
> In the meanwhile, lowering down the log priority will help to prevent the
> flooding.
>
> Fixes: 68c513e861ca ("net/mlx5: align implementation with modify API")
> Cc: michae...@nvidia.com
>
> Signed-off-by: Bing Zhao <bi...@nvidia.com>
> Acked-by: Ori Kam <or...@nvidia.com>
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
