From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153864 [PATCH v1 1/1] vhost: handle virtqueue locking for memory hotplug
Date: Thu, 29 May 2025 20:07:14 +0800 [thread overview]
Message-ID: <202505291207.54TC7Epk3497366@localhost.localdomain> (raw)
In-Reply-To: <20250529123226.1875075-2-dvo-plv@napatech.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/153864
_Compilation OK_
Submitter: Danylo Vodopianov <dvo-plv@napatech.com>
Date: Thu, 29 May 2025 14:32:26 +0200
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 3223019e73391066cbb0d248051b163e5373034c
153864 --> 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-05-29 12:43 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250529123226.1875075-2-dvo-plv@napatech.com>
2025-05-29 12:07 ` qemudev [this message]
2025-05-29 12:11 ` qemudev
2025-05-29 12:32 ` |WARNING| " checkpatch
2025-05-29 13:43 ` |SUCCESS| " 0-day Robot
2025-05-29 20:49 ` |SUCCESS| pw153864 [PATCH] [v1,1/1] vhost: handle virtqueue locking dpdklab
2025-05-29 21:09 ` |PENDING| " dpdklab
2025-05-29 21:26 ` |SUCCESS| " dpdklab
2025-05-29 21:53 ` dpdklab
2025-05-29 21:57 ` dpdklab
2025-05-29 21:59 ` dpdklab
2025-05-29 22:00 ` dpdklab
2025-05-29 22:13 ` |PENDING| " dpdklab
2025-05-29 22:13 ` dpdklab
2025-05-29 22:20 ` |SUCCESS| " dpdklab
2025-05-29 22:21 ` dpdklab
2025-05-29 23:04 ` dpdklab
2025-05-30 0:21 ` dpdklab
2025-05-30 1:01 ` |PENDING| " dpdklab
2025-05-30 1:28 ` dpdklab
2025-05-30 1:34 ` |SUCCESS| " dpdklab
2025-05-30 1:35 ` dpdklab
2025-05-30 1:36 ` |PENDING| " dpdklab
2025-05-30 1:41 ` |SUCCESS| " dpdklab
2025-05-30 1:55 ` dpdklab
2025-05-30 2:44 ` |PENDING| " dpdklab
2025-05-30 3:53 ` |WARNING| " dpdklab
2025-05-30 3:54 ` dpdklab
2025-05-30 3:54 ` dpdklab
2025-05-30 3:54 ` dpdklab
2025-05-30 3:55 ` dpdklab
2025-05-30 4:44 ` dpdklab
2025-05-30 5:47 ` |SUCCESS| " dpdklab
2025-05-30 5:49 ` dpdklab
2025-05-30 8:29 ` dpdklab
2025-05-30 9:18 ` dpdklab
2025-05-30 9:51 ` |WARNING| " dpdklab
2025-05-30 21:54 ` dpdklab
2025-05-30 22:02 ` dpdklab
2025-05-30 23:06 ` |SUCCESS| " dpdklab
2025-05-30 23:43 ` dpdklab
2025-05-31 2:11 ` dpdklab
2025-05-31 2:23 ` dpdklab
2025-05-31 2:36 ` dpdklab
2025-05-31 2:45 ` dpdklab
2025-06-04 13:11 ` dpdklab
2025-06-04 13:27 ` dpdklab
2025-06-10 19:57 ` 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=202505291207.54TC7Epk3497366@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).