public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Yang Xu <xu.yang3@zte.com.cn>,
	thomas@monjalon.net, dsosnowski@nvidia.com,
	viacheslavo@nvidia.com, bingz@nvidia.com, orika@nvidia.com,
	suanmingm@nvidia.com, matan@nvidia.com, yao.chenghu@zte.com.cn
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v3 1/1] net/mlx5: fix port down in link detection error branch
Date: Sun, 8 Feb 2026 18:36:13 +0200	[thread overview]
Message-ID: <8a880378-71f7-4f61-8089-4b44ea54d2c2@nvidia.com> (raw)
In-Reply-To: <20251126050948.3030776-1-xu.yang3@zte.com.cn>

Hi,


On 26/11/2025 7:09 AM, Yang Xu wrote:
> The port down state was not initialized in the error branch of link
> detection when MLX NIC link status update failed (ret < 0).
> This resulted in incorrect link state reporting, as the device
> retained stale link status instead of reflecting the actual down
> state under error conditions.
> 
> Fixes: 1256805dd54d ("net/mlx5: move Linux-specific functions")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Yang Xu <xu.yang3@zte.com.cn>

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh


  parent reply	other threads:[~2026-02-08 16:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251119060222.2814478-1-xu.yang3@zte.com.cn--in-reply-to=20251119060222.2814478-1-xu.yang3@zte.com.cn>
2025-11-26  5:09 ` [PATCH v3 1/1] net/mlx5: fix port down in link detection error branch Yang Xu
2026-02-05  9:12   ` Dariusz Sosnowski
2026-02-08 16:36   ` Raslan Darawsheh [this message]
2025-11-19  6:02 Yang Xu

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=8a880378-71f7-4f61-8089-4b44ea54d2c2@nvidia.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.com \
    --cc=xu.yang3@zte.com.cn \
    --cc=yao.chenghu@zte.com.cn \
    /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