From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: Rongwei Liu <rongweil@nvidia.com>
Subject: |WARNING| pw156701 [PATCH v1] net/mlx5: fix indirect action memory leak
Date: Wed, 17 Sep 2025 12:27:42 +0200 (CEST) [thread overview]
Message-ID: <20250917102742.DE9A6124077@dpdk.org> (raw)
In-Reply-To: <20250917102604.451241-1-rongweil@nvidia.com>
Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/156701
_coding style issues_
WARNING:BAD_FIXES_TAG: Please use correct Fixes: style 'Fixes: <12+ chars of sha1> ("<title line>")' - ie: 'Fixes: e26f50adbf38 ("net/mlx5: support indirect list meter mark action")'
#124:
Fixes: e26f50adb ("net/mlx5: support indirect list meter mark action")
total: 0 errors, 1 warnings, 0 checks, 7 lines checked
next prev parent reply other threads:[~2025-09-17 10:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250917102604.451241-1-rongweil@nvidia.com>
2025-09-17 10:01 ` |SUCCESS| " qemudev
2025-09-17 10:06 ` qemudev
2025-09-17 10:27 ` checkpatch [this message]
2025-09-17 10:56 ` |PENDING| pw156701 [PATCH] [v1] net/mlx5: fix indirect action memory dpdklab
2025-09-17 10:59 ` |SUCCESS| " dpdklab
2025-09-17 11:03 ` dpdklab
2025-09-17 11:07 ` dpdklab
2025-09-17 11:18 ` |PENDING| " dpdklab
2025-09-17 11:21 ` dpdklab
2025-09-17 11:25 ` |SUCCESS| " dpdklab
2025-09-17 11:28 ` dpdklab
2025-09-17 11:32 ` dpdklab
2025-09-17 11:32 ` dpdklab
2025-09-17 11:36 ` |PENDING| " dpdklab
2025-09-17 11:38 ` |SUCCESS| pw156701 [PATCH v1] net/mlx5: fix indirect action memory leak 0-day Robot
2025-09-17 11:38 ` 0-day Robot
2025-09-17 11:51 ` |SUCCESS| pw156701 [PATCH] [v1] net/mlx5: fix indirect action memory dpdklab
2025-09-17 11:54 ` dpdklab
2025-09-17 12:03 ` dpdklab
2025-09-17 12:12 ` dpdklab
2025-09-17 12:13 ` dpdklab
2025-09-17 12:20 ` dpdklab
2025-09-17 12:37 ` dpdklab
2025-09-17 12:43 ` dpdklab
2025-09-17 16:00 ` 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=20250917102742.DE9A6124077@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).