From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124870-124868 [PATCH 2/2] vhost: refactor to follow new naming convention
Date: Thu, 9 Mar 2023 09:56:52 +0800 [thread overview]
Message-ID: <202303090156.3291uq5W1334431@localhost.localdomain> (raw)
In-Reply-To: <20230309020721.22164-3-nmiki@yahoo-corp.jp>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124868
_Compilation OK_
Submitter: Nobuhiro MIKI <nmiki@yahoo-corp.jp>
Date: Thu, 9 Mar 2023 11:07:20 +0900
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: 1ce8d0c928ec85c9843fe00c1e1397b755ba539e
124870-124868 --> 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:[~2023-03-09 2:10 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309020721.22164-3-nmiki@yahoo-corp.jp>
2023-03-09 1:56 ` qemudev [this message]
2023-03-09 2:00 ` qemudev
2023-03-09 2:08 ` |WARNING| pw124868 " checkpatch
2023-03-09 4:19 ` |SUCCESS| " 0-day Robot
2023-03-09 3:10 |SUCCESS| pw124870-124868 [PATCH] [2/2] " dpdklab
2023-03-09 3:17 dpdklab
2023-03-09 3:20 dpdklab
2023-03-09 3:20 dpdklab
2023-03-09 3:22 dpdklab
2023-03-09 3:22 dpdklab
2023-03-09 3:26 dpdklab
2023-03-09 3:26 dpdklab
2023-03-09 3:28 dpdklab
2023-03-09 3:28 dpdklab
2023-03-09 3:31 dpdklab
2023-03-09 3:33 dpdklab
2023-03-09 3:36 dpdklab
2023-03-09 3:36 dpdklab
2023-03-09 3:37 dpdklab
2023-03-09 3:37 dpdklab
2023-03-09 3:41 dpdklab
2023-03-09 3:44 dpdklab
2023-03-09 3:45 dpdklab
2023-03-09 3:48 dpdklab
2023-03-09 3:48 dpdklab
2023-03-09 3:49 dpdklab
2023-03-09 3:50 dpdklab
2023-03-09 3:51 dpdklab
2023-03-09 3:53 dpdklab
2023-03-09 3:53 dpdklab
2023-03-09 3:55 dpdklab
2023-03-09 4:01 dpdklab
2023-03-09 4:04 dpdklab
2023-03-09 4:06 dpdklab
2023-03-09 4:06 dpdklab
2023-03-09 4:08 dpdklab
2023-03-09 4:10 dpdklab
2023-03-09 4:13 dpdklab
2023-03-09 4:22 dpdklab
2023-03-09 4:22 dpdklab
2023-03-09 4:26 dpdklab
2023-03-09 4:29 dpdklab
2023-03-09 4:30 dpdklab
2023-03-09 4:34 dpdklab
2023-03-09 4:42 dpdklab
2023-03-09 4:45 dpdklab
2023-03-09 4:46 dpdklab
2023-03-09 4:47 dpdklab
2023-03-09 4:48 dpdklab
2023-03-09 4:49 dpdklab
2023-03-09 4:50 dpdklab
2023-03-09 4:55 dpdklab
2023-03-09 5:00 dpdklab
2023-03-09 5:01 dpdklab
2023-03-09 5:03 dpdklab
2023-03-09 5:06 dpdklab
2023-03-09 5:15 dpdklab
2023-03-09 5:20 dpdklab
2023-03-09 5:21 dpdklab
2023-03-09 5:31 dpdklab
2023-03-09 5:37 dpdklab
2023-03-09 5:45 dpdklab
2023-03-09 5:46 dpdklab
2023-03-09 6:12 dpdklab
2023-03-09 7:54 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=202303090156.3291uq5W1334431@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).