From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw120877 [PATCH] vdpa/ifc: add live migration for block device
Date: Wed, 14 Dec 2022 18:18:44 +0800 [thread overview]
Message-ID: <202212141018.2BEAIiaZ2776995@localhost.localdomain> (raw)
In-Reply-To: <1671004060-62997-1-git-send-email-andy.pei@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/120877
_Compilation OK_
Submitter: Andy Pei <andy.pei@intel.com>
Date: Wed, 14 Dec 2022 15:47:40 +0800
DPDK git baseline: Repo:dpdk-next-virtio
Branch: main
CommitID: f262f16087ea6a77357a915cf4c0d10ddc7b6562
120877 --> 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 prev parent reply other threads:[~2022-12-14 10:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1671004060-62997-1-git-send-email-andy.pei@intel.com>
2022-12-14 8:39 ` checkpatch
2022-12-14 9:38 ` 0-day Robot
2022-12-14 10:18 ` qemudev [this message]
2022-12-14 10:22 ` qemudev
2022-12-14 12:47 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2022-12-14 12:05 dpdklab
2022-12-14 12:05 dpdklab
2022-12-14 12:04 dpdklab
2022-12-14 12:03 dpdklab
2022-12-14 12:02 dpdklab
2022-12-14 11:59 dpdklab
2022-12-14 11:56 dpdklab
2022-12-14 11:56 dpdklab
2022-12-14 11:54 dpdklab
2022-12-14 11:51 dpdklab
2022-12-14 11:49 dpdklab
2022-12-14 11:48 dpdklab
2022-12-14 11:38 dpdklab
2022-12-14 10:17 dpdklab
2022-12-14 9:39 dpdklab
2022-12-14 9:33 dpdklab
2022-12-14 9:31 dpdklab
2022-12-14 9:26 dpdklab
2022-12-14 9:23 dpdklab
2022-12-14 9:18 dpdklab
2022-12-14 9:18 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=202212141018.2BEAIiaZ2776995@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).