From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139069-139073 [PATCH v2 5/5] vhost: manage FD with epoll
Date: Wed, 3 Apr 2024 17:11:39 +0800 [thread overview]
Message-ID: <202404030911.4339BdXl1412807@localhost.localdomain> (raw)
In-Reply-To: <20240403092448.1361820-6-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139073
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Wed, 3 Apr 2024 11:24:44 +0200
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: deedfb86a7a6e10064d3cccd593f62072de96e36
139069-139073 --> 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-04-03 9:36 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240403092448.1361820-6-maxime.coquelin@redhat.com>
2024-04-03 9:11 ` qemudev [this message]
2024-04-03 9:15 ` qemudev
2024-04-03 9:26 ` |SUCCESS| pw139073 " checkpatch
2024-04-03 10:12 ` |SUCCESS| pw139069-139073 [PATCH] [v2,5/5] vhost: manage FD with epo dpdklab
2024-04-03 10:12 ` dpdklab
2024-04-03 10:14 ` dpdklab
2024-04-03 10:14 ` dpdklab
2024-04-03 10:14 ` dpdklab
2024-04-03 10:15 ` dpdklab
2024-04-03 10:15 ` dpdklab
2024-04-03 10:15 ` dpdklab
2024-04-03 10:16 ` dpdklab
2024-04-03 10:17 ` dpdklab
2024-04-03 10:17 ` dpdklab
2024-04-03 10:18 ` dpdklab
2024-04-03 10:18 ` dpdklab
2024-04-03 10:18 ` dpdklab
2024-04-03 10:18 ` dpdklab
2024-04-03 10:19 ` dpdklab
2024-04-03 10:19 ` dpdklab
2024-04-03 10:20 ` dpdklab
2024-04-03 10:20 ` dpdklab
2024-04-03 10:21 ` dpdklab
2024-04-03 10:21 ` dpdklab
2024-04-03 10:22 ` dpdklab
2024-04-03 10:22 ` dpdklab
2024-04-03 10:22 ` dpdklab
2024-04-03 10:22 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:23 ` dpdklab
2024-04-03 10:24 ` dpdklab
2024-04-03 10:24 ` dpdklab
2024-04-03 10:24 ` dpdklab
2024-04-03 10:24 ` dpdklab
2024-04-03 10:24 ` dpdklab
2024-04-03 10:25 ` dpdklab
2024-04-03 10:25 ` dpdklab
2024-04-03 10:25 ` dpdklab
2024-04-03 10:26 ` dpdklab
2024-04-03 10:26 ` dpdklab
2024-04-03 10:26 ` |SUCCESS| pw139073 [PATCH v2 5/5] vhost: manage FD with epoll 0-day Robot
2024-04-03 10:26 ` |SUCCESS| pw139069-139073 [PATCH] [v2,5/5] vhost: manage FD with epo dpdklab
2024-04-03 10:27 ` dpdklab
2024-04-03 10:27 ` dpdklab
2024-04-03 10:27 ` dpdklab
2024-04-03 10:28 ` dpdklab
2024-04-03 10:28 ` dpdklab
2024-04-03 10:29 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:30 ` dpdklab
2024-04-03 10:31 ` dpdklab
2024-04-03 10:31 ` dpdklab
2024-04-03 10:32 ` dpdklab
2024-04-03 10:33 ` dpdklab
2024-04-03 10:34 ` dpdklab
2024-04-03 10:37 ` dpdklab
2024-04-03 10:38 ` dpdklab
2024-04-03 10:38 ` dpdklab
2024-04-03 10:39 ` dpdklab
2024-04-03 10:40 ` dpdklab
2024-04-03 10:42 ` dpdklab
2024-04-03 10:42 ` dpdklab
2024-04-03 10:43 ` dpdklab
2024-04-03 10:45 ` dpdklab
2024-04-03 10:46 ` dpdklab
2024-04-03 10:47 ` dpdklab
2024-04-03 10:51 ` dpdklab
2024-04-03 10:52 ` dpdklab
2024-04-03 10:52 ` dpdklab
2024-04-03 11:01 ` dpdklab
2024-04-03 11:01 ` dpdklab
2024-04-03 11:08 ` dpdklab
2024-04-03 11:13 ` dpdklab
2024-04-03 11:36 ` dpdklab
2024-04-03 11:44 ` dpdklab
2024-04-03 11:45 ` dpdklab
2024-04-03 14:30 ` dpdklab
2024-04-03 15:10 ` dpdklab
2024-04-04 6:09 ` dpdklab
2024-04-04 6:14 ` dpdklab
2024-04-04 6:18 ` dpdklab
2024-04-04 6:23 ` dpdklab
2024-04-04 6:43 ` 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=202404030911.4339BdXl1412807@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).