automatic DPDK test reports
 help / color / mirror / Atom feed
From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Yang Xu <xu.yang3@zte.com.cn>
Subject: |WARNING| pw158890 [PATCH v3 1/1] net/mlx5: fix port down in link detection error branch
Date: Wed, 19 Nov 2025 07:03:37 +0100 (CET)	[thread overview]
Message-ID: <20251119060337.882101261F1@dpdk.org> (raw)
In-Reply-To: <20251119060222.2814478-1-xu.yang3@zte.com.cn>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/158890

_coding style issues_

Must be a reply to the first patch (--in-reply-to).


WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 1256805dd54d ("net/mlx5: move Linux-specific functions")'
#73: 
Fixes: 1256805dd54 ("net/mlx5: move Linux-specific functions")

total: 0 errors, 1 warnings, 0 checks, 11 lines checked

  parent reply	other threads:[~2025-11-19  6:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20251119060222.2814478-1-xu.yang3@zte.com.cn>
2025-11-19  5:29 ` |SUCCESS| " qemudev
2025-11-19  5:34 ` qemudev
2025-11-19  6:03 ` checkpatch [this message]
2025-11-19  7:10 ` 0-day Robot
2025-11-19  7:10 ` 0-day Robot
2025-11-19  8:37 ` |PENDING| pw158890 [PATCH] [v3,1/1] net/mlx5: fix port down in link dpdklab
2025-11-19  8:39 ` |SUCCESS| " dpdklab
2025-11-19  8:42 ` |PENDING| " dpdklab
2025-11-19  8:44 ` |SUCCESS| " dpdklab
2025-11-19  8:54 ` dpdklab
2025-11-19  8:55 ` dpdklab
2025-11-19  8:55 ` dpdklab
2025-11-19  9:05 ` |PENDING| " dpdklab
2025-11-19  9:09 ` dpdklab
2025-11-19  9:09 ` |SUCCESS| " dpdklab
2025-11-19  9:10 ` |PENDING| " dpdklab
2025-11-19  9:23 ` |SUCCESS| " dpdklab
2025-11-19  9:32 ` dpdklab
2025-11-19  9:44 ` dpdklab
2025-11-19  9:55 ` dpdklab
2025-11-19 10:16 ` dpdklab

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=20251119060337.882101261F1@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=test-report@dpdk.org \
    --cc=xu.yang3@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;
as well as URLs for NNTP newsgroup(s).