From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137494-137496 [PATCH v2 3/3] net/virtio_user: support sharing vq descriptor IOVA to the backend
Date: Thu, 29 Feb 2024 21:07:31 +0800 [thread overview]
Message-ID: <202402291307.41TD7VB12218934@localhost.localdomain> (raw)
In-Reply-To: <20240229132919.2186118-4-schalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/137496
_Compilation OK_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Thu, 29 Feb 2024 18:59:17 +0530
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 92c0ad70caf3ed6f4b93de6ddaf7bc369737c049
137494-137496 --> 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:[~2024-02-29 13:32 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240229132919.2186118-4-schalla@marvell.com>
2024-02-29 13:07 ` qemudev [this message]
2024-02-29 13:11 ` qemudev
2024-02-29 13:31 ` |SUCCESS| pw137496 " checkpatch
2024-02-29 14:25 ` 0-day Robot
2024-02-29 15:00 ` |SUCCESS| pw137494-137496 [PATCH] [v2,3/3] net/virtio_user: support dpdklab
2024-02-29 15:02 ` dpdklab
2024-02-29 15:03 ` dpdklab
2024-02-29 15:07 ` dpdklab
2024-02-29 15:33 ` dpdklab
2024-02-29 15:34 ` dpdklab
2024-02-29 15:37 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 15:42 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 15:47 ` dpdklab
2024-02-29 16:05 ` dpdklab
2024-02-29 16:06 ` dpdklab
2024-02-29 16:06 ` dpdklab
2024-02-29 16:08 ` dpdklab
2024-02-29 16:09 ` dpdklab
2024-02-29 16:14 ` dpdklab
2024-02-29 16:14 ` dpdklab
2024-02-29 17:04 ` dpdklab
2024-02-29 17:05 ` dpdklab
2024-02-29 17:14 ` dpdklab
2024-02-29 17:14 ` dpdklab
2024-02-29 17:14 ` dpdklab
2024-02-29 17:14 ` dpdklab
2024-02-29 17:14 ` dpdklab
2024-02-29 17:15 ` dpdklab
2024-02-29 17:15 ` dpdklab
2024-02-29 17:18 ` dpdklab
2024-02-29 17:19 ` dpdklab
2024-02-29 17:19 ` dpdklab
2024-02-29 17:19 ` dpdklab
2024-02-29 17:20 ` dpdklab
2024-02-29 17:20 ` dpdklab
2024-02-29 17:21 ` dpdklab
2024-02-29 17:29 ` dpdklab
2024-02-29 17:29 ` dpdklab
2024-02-29 17:30 ` dpdklab
2024-02-29 17:30 ` dpdklab
2024-02-29 17:31 ` dpdklab
2024-02-29 17:31 ` dpdklab
2024-02-29 17:31 ` dpdklab
2024-02-29 17:32 ` dpdklab
2024-02-29 17:32 ` dpdklab
2024-02-29 17:33 ` dpdklab
2024-02-29 17:34 ` dpdklab
2024-02-29 17:34 ` dpdklab
2024-02-29 17:34 ` dpdklab
2024-02-29 17:34 ` dpdklab
2024-02-29 17:35 ` dpdklab
2024-02-29 17:35 ` dpdklab
2024-02-29 17:35 ` dpdklab
2024-02-29 17:39 ` dpdklab
2024-02-29 17:39 ` dpdklab
2024-02-29 17:39 ` dpdklab
2024-02-29 17:40 ` dpdklab
2024-02-29 17:43 ` dpdklab
2024-02-29 17:48 ` dpdklab
2024-02-29 17:51 ` dpdklab
2024-02-29 17:51 ` dpdklab
2024-02-29 17:52 ` dpdklab
2024-02-29 17:56 ` dpdklab
2024-02-29 18:02 ` dpdklab
2024-02-29 18:46 ` dpdklab
2024-02-29 19:22 ` dpdklab
2024-02-29 23:12 ` dpdklab
2024-03-01 7:22 ` dpdklab
2024-03-01 7:27 ` dpdklab
2024-03-01 7:32 ` dpdklab
2024-03-01 7:37 ` dpdklab
2024-03-02 7:08 ` dpdklab
2024-03-03 4:42 ` dpdklab
2024-03-03 5:32 ` dpdklab
2024-03-03 5:59 ` 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=202402291307.41TD7VB12218934@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).