public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
	Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
	Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Suanming Mou <suanmingm@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Gregory Etelson <getelson@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix flex item capability check
Date: Tue, 24 Mar 2026 15:03:11 +0200	[thread overview]
Message-ID: <a0aed7a7-a6de-4ea2-a44c-e5e1c71841e6@nvidia.com> (raw)
In-Reply-To: <20260323102059.791194-1-dsosnowski@nvidia.com>

Hi,


On 23/03/2026 12:20 PM, Dariusz Sosnowski wrote:
> Whenever installed BlueField FW was too old and it did not support
> flex parser, mlx5 PMD reported an unrelated error
> on flex item creation.
> For example it reported that:
> 
>      unsupported header length field mode (FIXED)
> 
> This was caused by lack of check for flex parser support.
> 
> This patch adds missing capability check and
> adds proper error reporting.
> Limitations of flex item described in PMD docs are also adjusted.
> 
> Fixes: 71adf25dbfb3 ("net/mlx5: fix flex item availability")
> Cc: getelson@nvidia.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


      reply	other threads:[~2026-03-24 13:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-23 10:20 [PATCH] net/mlx5: fix flex item capability check Dariusz Sosnowski
2026-03-24 13:03 ` Raslan Darawsheh [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=a0aed7a7-a6de-4ea2-a44c-e5e1c71841e6@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=viacheslavo@nvidia.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