From: checkpatch@dpdk.org
To: test-report@dpdk.org
Subject: |SUCCESS| pw153169 [PATCH 2/2] net/mlx5: fix coverity warning
Date: Sun, 27 Apr 2025 13:23:53 +0200 (CEST) [thread overview]
Message-ID: <20250427112353.317061251C3@dpdk.org> (raw)
In-Reply-To: <20250427112257.108544-2-mkashani@nvidia.com>
Test-Label: checkpatch
Test-Status: SUCCESS
http://dpdk.org/patch/153169
_coding style OK_
next prev parent reply other threads:[~2025-04-27 11:23 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250427112257.108544-2-mkashani@nvidia.com>
2025-04-27 10:59 ` |SUCCESS| pw153168-153169 " qemudev
2025-04-27 11:03 ` qemudev
2025-04-27 11:23 ` checkpatch [this message]
2025-04-27 12:44 ` |SUCCESS| pw153169 " 0-day Robot
2025-04-28 9:19 ` |SUCCESS| pw153168-153169 [PATCH] [2/2] net/mlx5: fix coverity warni dpdklab
2025-04-28 9:40 ` dpdklab
2025-04-28 9:40 ` dpdklab
2025-04-28 9:47 ` dpdklab
2025-04-28 9:50 ` dpdklab
2025-04-28 9:51 ` dpdklab
2025-04-28 9:51 ` dpdklab
2025-04-28 9:59 ` |PENDING| " dpdklab
2025-04-28 9:59 ` |SUCCESS| " dpdklab
2025-04-28 10:01 ` dpdklab
2025-04-28 10:05 ` dpdklab
2025-04-28 10:15 ` dpdklab
2025-04-28 10:16 ` |PENDING| " dpdklab
2025-04-28 11:40 ` dpdklab
2025-04-28 12:30 ` |SUCCESS| " dpdklab
2025-04-28 12:32 ` |PENDING| " dpdklab
2025-04-28 12:47 ` |SUCCESS| " dpdklab
2025-04-28 12:48 ` dpdklab
2025-04-28 13:21 ` dpdklab
2025-04-28 13:55 ` dpdklab
2025-04-28 14:43 ` dpdklab
2025-04-28 16:14 ` dpdklab
2025-04-28 23:52 ` |FAILURE| " dpdklab
2025-04-29 22:02 ` |SUCCESS| " dpdklab
2025-04-29 22:13 ` dpdklab
2025-04-29 22:27 ` dpdklab
2025-04-29 22:41 ` dpdklab
2025-04-29 22:58 ` dpdklab
2025-04-29 23:00 ` dpdklab
2025-04-29 23:04 ` dpdklab
2025-04-29 23:06 ` dpdklab
2025-04-29 23:12 ` dpdklab
2025-04-29 23:25 ` dpdklab
2025-04-29 23:59 ` dpdklab
2025-04-30 0:21 ` dpdklab
2025-04-30 1:11 ` 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=20250427112353.317061251C3@dpdk.org \
--to=checkpatch@dpdk.org \
--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).