From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw157578-157597 [PATCH 21/21] net/ena: upgrade driver version to 2.14.0
Date: Wed, 15 Oct 2025 14:47:54 +0800 [thread overview]
Message-ID: <202510150647.59F6lsgH177450@localhost.localdomain> (raw)
In-Reply-To: <20251015071730.1286-1-shaibran@amazon.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/157597
_Compilation OK_
Submitter: Shai Brandes <shaibran@amazon.com>
Date: Wed, 15 Oct 2025 10:06:47 +0300
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7cacb5b3f6cc89785f9383ac9544e61dc971897d
157578-157597 --> meson & ninja build successfully
Test environment and result as below:
+---------------------+----------------+
| Environment | compilation |
+---------------------+----------------+
| Loongnix-Server 8.3 | PASS |
+---------------------+----------------+
Loongnix-Server 8.3
Kernel: 4.19.190+
Compiler: gcc 8.3
next parent reply other threads:[~2025-10-15 7:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251015071730.1286-1-shaibran@amazon.com>
2025-10-15 6:47 ` qemudev [this message]
2025-10-15 6:52 ` qemudev
2025-10-15 7:19 ` |SUCCESS| pw157597 " checkpatch
2025-10-15 7:50 ` |PENDING| pw157578-157597 [PATCH] [21/21] net/ena: upgrade driver ve dpdklab
2025-10-15 7:52 ` dpdklab
2025-10-15 7:54 ` |SUCCESS| " dpdklab
2025-10-15 7:58 ` dpdklab
2025-10-15 8:02 ` |PENDING| " dpdklab
2025-10-15 8:06 ` dpdklab
2025-10-15 8:07 ` dpdklab
2025-10-15 8:13 ` |SUCCESS| " dpdklab
2025-10-15 8:16 ` dpdklab
2025-10-15 8:16 ` dpdklab
2025-10-15 8:25 ` dpdklab
2025-10-15 8:28 ` dpdklab
2025-10-15 8:31 ` |FAILURE| pw157597 [PATCH 21/21] net/ena: upgrade driver version to 2.14.0 0-day Robot
2025-10-15 8:33 ` |SUCCESS| pw157578-157597 [PATCH] [21/21] net/ena: upgrade driver ve dpdklab
2025-10-15 8:35 ` dpdklab
2025-10-15 8:42 ` dpdklab
2025-10-15 8:43 ` dpdklab
2025-10-15 8:47 ` dpdklab
2025-10-15 12:42 ` dpdklab
2025-10-15 16:32 ` 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=202510150647.59F6lsgH177450@localhost.localdomain \
--to=qemudev@loongson.cn \
--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).