From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw147087-147092 [PATCH v3 6/6] vhost: move VDUSE reconnection after device is created
Date: Thu, 24 Oct 2024 17:13:15 +0800 [thread overview]
Message-ID: <202410240913.49O9DFEE1695290@localhost.localdomain> (raw)
In-Reply-To: <20241024094406.3826637-7-maxime.coquelin@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/147092
_Compilation OK_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Thu, 24 Oct 2024 11:44:01 +0200
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 90cb8ff8196f9b9c1c2bcee1c94ea583789bb63f
147087-147092 --> 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-10-24 9:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241024094406.3826637-7-maxime.coquelin@redhat.com>
2024-10-24 9:13 ` qemudev [this message]
2024-10-24 9:17 ` qemudev
2024-10-24 9:45 ` |WARNING| pw147092 " checkpatch
2024-10-24 10:47 ` |SUCCESS| " 0-day Robot
2024-10-24 13:15 ` |SUCCESS| pw147087-147092 [PATCH] [v3,6/6] vhost: move VDUSE reconne dpdklab
2024-10-24 13:34 ` dpdklab
2024-10-24 13:40 ` dpdklab
2024-10-24 13:45 ` dpdklab
2024-10-24 14:13 ` dpdklab
2024-10-25 9:02 ` dpdklab
2024-10-25 9:20 ` dpdklab
2024-10-26 3:20 ` dpdklab
2024-10-26 3:46 ` |PENDING| " dpdklab
2024-10-26 15:12 ` |SUCCESS| " dpdklab
2024-10-26 17:51 ` dpdklab
2024-10-26 18:13 ` dpdklab
2024-10-26 19:05 ` dpdklab
2024-10-26 19:42 ` dpdklab
2024-10-26 20:05 ` dpdklab
2024-10-26 20:28 ` dpdklab
2024-10-26 21:36 ` dpdklab
2024-10-30 6:25 ` dpdklab
2024-11-01 21: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=202410240913.49O9DFEE1695290@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).