From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw153806 [PATCH] net/mlx5: avoid setting kernel MTU if not
Date: Wed, 28 May 2025 14:12:23 -0700 (PDT) [thread overview]
Message-ID: <68377c37.050a0220.d8952.4349SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20250528093644.2456221-1-maxime.coquelin@redhat.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/153806
_Functional Testing PASS_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wednesday, May 28 2025 09:36:44
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:e43585acf22932bc32617f092257795122ced05c
153806 --> functional testing pass
Upstream job id: Template-DTS-Pipeline#228114
Test environment and result as below:
Arm Ampere Altra - Ubuntu 22.04
Kernel: 5.15.83+
Compiler: gcc 11.4
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/33264/
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-05-28 21:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250528093644.2456221-1-maxime.coquelin@redhat.com>
2025-05-28 9:09 ` |SUCCESS| pw153806 [PATCH] net/mlx5: avoid setting kernel MTU if not needed qemudev
2025-05-28 9:13 ` qemudev
2025-05-28 9:37 ` checkpatch
2025-05-28 10:45 ` 0-day Robot
2025-05-28 18:28 ` |SUCCESS| pw153806 [PATCH] net/mlx5: avoid setting kernel MTU if not dpdklab
2025-05-28 19:24 ` dpdklab
2025-05-28 19:59 ` |PENDING| " dpdklab
2025-05-28 20:32 ` |SUCCESS| " dpdklab
2025-05-28 20:33 ` dpdklab
2025-05-28 20:33 ` dpdklab
2025-05-28 20:34 ` dpdklab
2025-05-28 20:36 ` dpdklab
2025-05-28 21:12 ` dpdklab [this message]
2025-05-28 21:21 ` |PENDING| " dpdklab
2025-05-28 21:24 ` dpdklab
2025-05-28 21:31 ` dpdklab
2025-05-28 22:06 ` |SUCCESS| " dpdklab
2025-05-28 22:35 ` dpdklab
2025-05-28 23:10 ` |PENDING| " dpdklab
2025-05-28 23:21 ` |WARNING| " dpdklab
2025-05-28 23:30 ` dpdklab
2025-05-29 1:36 ` dpdklab
2025-05-29 1:49 ` |SUCCESS| " dpdklab
2025-05-29 1:49 ` dpdklab
2025-05-29 2:33 ` |WARNING| " dpdklab
2025-05-29 3:35 ` |SUCCESS| " dpdklab
2025-05-29 3:37 ` dpdklab
2025-05-29 3:38 ` dpdklab
2025-05-29 3:40 ` dpdklab
2025-05-29 4:29 ` |WARNING| " dpdklab
2025-05-29 6:29 ` |SUCCESS| " dpdklab
2025-05-29 7:18 ` |WARNING| " dpdklab
2025-05-29 11:56 ` |SUCCESS| " dpdklab
2025-05-30 2:38 ` dpdklab
2025-05-30 3:18 ` |WARNING| " dpdklab
2025-05-30 3:44 ` |SUCCESS| " dpdklab
2025-05-30 4:08 ` |WARNING| " dpdklab
2025-05-30 8:01 ` dpdklab
2025-06-04 7:35 ` |SUCCESS| " dpdklab
2025-06-04 8: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=68377c37.050a0220.d8952.4349SMTPIN_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).