From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu,
Stephen Hemminger <stephen@networkplumber.org>
Subject: |SUCCESS| pw157260 [PATCH] ethdev: fix copy-paste error in fn parame
Date: Fri, 03 Oct 2025 06:49:31 -0700 (PDT) [thread overview]
Message-ID: <68dfd46b.050a0220.3519c1.5bf9SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20251003110944.1594659-1-bruce.richardson@intel.com>
Test-Label: iol-compile-amd64-testing
Test-Status: SUCCESS
http://dpdk.org/patch/157260
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Friday, October 03 2025 11:09:44
DPDK git baseline: Repo:dpdk-next-net
Branch: master
CommitID:c04bbd131b2c14b3049bf86d3ef367b34e6fdf1e
157260 --> testing pass
Upstream job id: Windows-Compile-DPDK-Native#31400
Test environment and result as below:
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Environment | dpdk_meson_compile | dpdk_msvc_compile | dpdk_llvm_clang_compile | dpdk_mingw64_compile |
+=====================+====================+===================+=========================+======================+
| Ubuntu 20.04 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| FreeBSD 14.2 | PASS | SKIPPED | SKIPPED | SKIPPED |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
| Windows Server 2022 | SKIPPED | PASS | PASS | PASS |
+---------------------+--------------------+-------------------+-------------------------+----------------------+
Ubuntu 20.04
Kernel: 4.19
Compiler: gcc gcc (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
FreeBSD 14.2
Kernel: 14.2-RELEASE
Compiler: clang 18.1.6
Windows Server 2022
Kernel: 10.0.20348.2031
Compiler: clang 15.0.7, gcc 14.1.0 (MinGW), and MSVC VS 19.39.33521
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/34208/
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-10-03 13:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251003110944.1594659-1-bruce.richardson@intel.com>
2025-10-03 10:45 ` |SUCCESS| pw157260 [PATCH] ethdev: fix copy-paste error in fn parameter description qemudev
2025-10-03 10:50 ` qemudev
2025-10-03 11:11 ` checkpatch
2025-10-03 11:38 ` |PENDING| pw157260 [PATCH] ethdev: fix copy-paste error in fn parame dpdklab
2025-10-03 11:39 ` dpdklab
2025-10-03 11:39 ` |SUCCESS| " dpdklab
2025-10-03 11:44 ` dpdklab
2025-10-03 11:49 ` |PENDING| " dpdklab
2025-10-03 11:49 ` dpdklab
2025-10-03 11:58 ` |SUCCESS| " dpdklab
2025-10-03 12:19 ` dpdklab
2025-10-03 12:23 ` |FAILURE| pw157260 [PATCH] ethdev: fix copy-paste error in fn parameter description 0-day Robot
2025-10-03 12:29 ` |SUCCESS| pw157260 [PATCH] ethdev: fix copy-paste error in fn parame dpdklab
2025-10-03 12:33 ` dpdklab
2025-10-03 12:40 ` dpdklab
2025-10-03 12:41 ` dpdklab
2025-10-03 12:50 ` dpdklab
2025-10-03 12:55 ` dpdklab
2025-10-03 13:17 ` dpdklab
2025-10-03 13:39 ` dpdklab
2025-10-03 13:49 ` 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=68dfd46b.050a0220.3519c1.5bf9SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=stephen@networkplumber.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).