From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rongwei Liu <rongweil@nvidia.com>
Subject: |WARNING| pw156216 [PATCH v1] net/mlx5: fix probe optimization race condition
Date: Thu, 28 Aug 2025 05:21:37 +0200 (CEST) [thread overview]
Message-ID: <20250828032138.02893124004@dpdk.org> (raw)
In-Reply-To: <20250828032134.167999-1-rongweil@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/156216
_coding style issues_
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: 51fb5c40c826 ("common/mlx5: optimize device probing")'
#127:
Fixes: 51fb5c40c826 ("net/mlx5: optimize device probing")
total: 0 errors, 1 warnings, 0 checks, 145 lines checked
next prev parent reply other threads:[~2025-08-28 3:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250828032134.167999-1-rongweil@nvidia.com>
2025-08-28 2:49 ` |SUCCESS| " qemudev
2025-08-28 2:54 ` qemudev
2025-08-28 3:21 ` checkpatch [this message]
2025-08-28 4:07 ` |PENDING| pw156216 [PATCH] [v1] net/mlx5: fix probe optimization rac dpdklab
2025-08-28 4:11 ` |SUCCESS| " dpdklab
2025-08-28 4:13 ` dpdklab
2025-08-28 4:15 ` dpdklab
2025-08-28 4:18 ` dpdklab
2025-08-28 4:24 ` |SUCCESS| pw156216 [PATCH v1] net/mlx5: fix probe optimization race condition 0-day Robot
2025-08-28 4:32 ` |SUCCESS| pw156216 [PATCH] [v1] net/mlx5: fix probe optimization rac dpdklab
2025-08-28 4:40 ` dpdklab
2025-08-28 5:17 ` dpdklab
2025-08-28 5:38 ` dpdklab
2025-08-28 5:38 ` dpdklab
2025-08-28 6:21 ` |PENDING| " dpdklab
2025-08-28 6:39 ` |SUCCESS| " dpdklab
2025-08-28 6:45 ` dpdklab
2025-08-28 6:55 ` |PENDING| " dpdklab
2025-08-28 8:28 ` |SUCCESS| " dpdklab
2025-08-28 10:20 ` dpdklab
2025-08-28 10:46 ` dpdklab
2025-08-28 13:22 ` |PENDING| " dpdklab
2025-08-28 13:32 ` |WARNING| " dpdklab
2025-08-28 14:19 ` 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=20250828032138.02893124004@dpdk.org \
--to=checkpatch@dpdk.org \
--cc=rongweil@nvidia.com \
--cc=test-report@dpdk.org \
/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).