From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw158794-158812 [PATCH v2 19/19] vfio: introduce cdev mode
Date: Sat, 15 Nov 2025 01:10:21 +0800 [thread overview]
Message-ID: <202511141710.5AEHAL9r800822@localhost.localdomain> (raw)
In-Reply-To: <45db9c5e1589c56ed0e31a0e15390da5366ca5c2.1763142008.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/158812
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Fri, 14 Nov 2025 17:40:11 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: be0112878b4fc3a1b918370ed2fe615c52039d77
158794-158812 --> 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-11-14 17:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45db9c5e1589c56ed0e31a0e15390da5366ca5c2.1763142008.git.anatoly.burakov@intel.com>
2025-11-14 17:10 ` qemudev [this message]
2025-11-14 17:15 ` qemudev
2025-11-14 17:44 ` |SUCCESS| pw158812 " checkpatch
2025-11-14 18:12 ` |FAILURE| pw158794-158812 [PATCH] [v2,19/19] vfio: introduce cdev mo dpdklab
2025-11-14 18:15 ` dpdklab
2025-11-14 18:16 ` |SUCCESS| " dpdklab
2025-11-14 18:22 ` |FAILURE| " dpdklab
2025-11-14 18:24 ` |PENDING| " dpdklab
2025-11-14 18:27 ` |SUCCESS| " dpdklab
2025-11-14 18:36 ` dpdklab
2025-11-14 18:40 ` |PENDING| " dpdklab
2025-11-14 18:48 ` |FAILURE| pw158812 [PATCH v2 19/19] vfio: introduce cdev mode 0-day Robot
2025-11-14 18:52 ` |SUCCESS| pw158794-158812 [PATCH] [v2,19/19] vfio: introduce cdev mo dpdklab
2025-11-14 19:04 ` dpdklab
2025-11-14 19:11 ` |FAILURE| " dpdklab
2025-11-14 19:14 ` dpdklab
2025-11-14 19:46 ` |SUCCESS| " dpdklab
2025-11-14 21:33 ` dpdklab
2025-11-15 0:58 ` |FAILURE| " dpdklab
2025-11-15 4:26 ` dpdklab
2025-11-15 5:00 ` dpdklab
2025-11-15 8:09 ` |SUCCESS| " dpdklab
2025-11-15 8:21 ` dpdklab
2025-11-15 10:48 ` |FAILURE| " dpdklab
2025-11-15 11:05 ` dpdklab
2025-11-15 13:18 ` dpdklab
2025-11-15 13:24 ` dpdklab
2025-11-15 14:39 ` dpdklab
2025-11-15 14:39 ` dpdklab
2025-11-15 14:39 ` dpdklab
2025-11-15 16:32 ` dpdklab
2025-11-15 16:34 ` dpdklab
2025-11-15 16:36 ` dpdklab
2025-11-15 16:37 ` dpdklab
2025-11-15 16:39 ` dpdklab
2025-11-15 16:41 ` dpdklab
2025-11-15 16:43 ` dpdklab
2025-11-15 16:45 ` dpdklab
2025-11-15 16:47 ` dpdklab
2025-11-15 16:48 ` dpdklab
2025-11-15 16:50 ` dpdklab
2025-11-15 16:52 ` dpdklab
2025-11-15 16:53 ` dpdklab
2025-11-15 16:55 ` dpdklab
2025-11-15 16:56 ` |WARNING| " 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=202511141710.5AEHAL9r800822@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).