From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw159103 [PATCH] net/mlx5: fix register selection for meta
Date: Mon, 01 Dec 2025 12:28:47 -0800 (PST) [thread overview]
Message-ID: <692dfa7f.050a0220.68cc8.bafaSMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251201173628.266032-1-getelson@nvidia.com>
Test-Label: iol-sample-apps-testing
Test-Status: SUCCESS
http://dpdk.org/patch/159103
_Testing PASS_
Submitter: Gregory Etelson <getelson@nvidia.com>
Date: Monday, December 01 2025 17:36:27
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: master
CommitID:2815d5065694eb9d0b43c312d17a00d2356e36f1
159103 --> testing pass
Upstream job id: ACVP-FIPS-testing#11971
Test environment and result as below:
+--------------+----------------------+
| Environment | dpdk_fips_validation |
+==============+======================+
| Ubuntu 20.04 | PASS |
+--------------+----------------------+
Ubuntu 20.04
Kernel: 5.15
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34704/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
prev parent reply other threads:[~2025-12-01 20:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251201173628.266032-1-getelson@nvidia.com>
2025-12-01 17:08 ` |SUCCESS| pw159103 [PATCH] net/mlx5: fix register selection for metadata between E-Switch and VM qemudev
2025-12-01 17:13 ` qemudev
2025-12-01 17:36 ` checkpatch
2025-12-01 18:47 ` |PENDING| pw159103 [PATCH] net/mlx5: fix register selection for meta dpdklab
2025-12-01 18:47 ` dpdklab
2025-12-01 18:48 ` dpdklab
2025-12-01 18:57 ` dpdklab
2025-12-01 19:48 ` |SUCCESS| " dpdklab
2025-12-01 20:01 ` dpdklab
2025-12-01 20:28 ` dpdklab [this message]
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=692dfa7f.050a0220.68cc8.bafaSMTPIN_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).