From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw155078 [PATCH] [v3] net/mlx5: remove use of sizeof(rte_v
Date: Tue, 08 Jul 2025 10:49:51 -0700 (PDT) [thread overview]
Message-ID: <686d5a3f.050a0220.2c7307.889bSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <1751987516-30482-1-git-send-email-andremue@linux.microsoft.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/155078
_Functional Testing PASS_
Submitter: Andre Muezerie <andremue@linux.microsoft.com>
Date: Tuesday, July 08 2025 15:11:56
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e2888614268cbf0abcc7cd72ad97ff4e4901d0a5
155078 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#235725
Test environment and result as below:
Ubuntu 22.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
NIC: Intel Corporation QAT 8970 0 Mbps
Aggregate Results by Test Suite
+----------------------------+--------+
| Test Suite | Result |
+============================+========+
| crypto_perf_cryptodev_perf | PASS |
+----------------------------+--------+
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/33615/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2025-07-08 17:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1751987516-30482-1-git-send-email-andremue@linux.microsoft.com>
2025-07-08 14:37 ` |SUCCESS| pw155078 [PATCH v3] net/mlx5: remove use of sizeof(rte_v128u32_t) qemudev
2025-07-08 14:42 ` qemudev
2025-07-08 15:11 ` |SUCCESS| pw155078 [PATCH v3] net/mlx5: remove use of sizeofrte_v128u32_t checkpatch
2025-07-08 16:24 ` |SUCCESS| pw155078 [PATCH v3] net/mlx5: remove use of sizeof(rte_v128u32_t) 0-day Robot
2025-07-08 17:45 ` |PENDING| pw155078 [PATCH] [v3] net/mlx5: remove use of sizeof(rte_v dpdklab
2025-07-08 17:49 ` dpdklab [this message]
2025-07-08 17:50 ` |SUCCESS| " dpdklab
2025-07-08 18:43 ` |PENDING| " dpdklab
2025-07-08 19:05 ` dpdklab
2025-07-08 19:06 ` dpdklab
2025-07-08 19:49 ` |SUCCESS| " dpdklab
2025-07-08 20:02 ` dpdklab
2025-07-08 20:04 ` dpdklab
2025-07-08 20:04 ` dpdklab
2025-07-08 20:05 ` dpdklab
2025-07-08 20:05 ` dpdklab
2025-07-08 20:08 ` dpdklab
2025-07-08 20:08 ` dpdklab
2025-07-08 20:08 ` dpdklab
2025-07-08 20:28 ` dpdklab
2025-07-08 20:45 ` dpdklab
2025-07-08 20:58 ` |WARNING| " dpdklab
2025-07-08 21:41 ` dpdklab
2025-07-08 22:40 ` |SUCCESS| " 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=686d5a3f.050a0220.2c7307.889bSMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--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).