From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129183 [PATCH] doc: add ice VF live migration guide
Date: Mon, 3 Jul 2023 13:06:12 +0800 [thread overview]
Message-ID: <202307030506.36356Ce63049268@localhost.localdomain> (raw)
In-Reply-To: <20230703051449.191259-1-lingyu.liu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129183
_Compilation OK_
Submitter: Lingyu Liu <lingyu.liu@intel.com>
Date: Mon, 3 Jul 2023 05:14:49 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 175c6284cad3413a643ce74065cb509a3e0f49bf
129183 --> 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-07-03 5:20 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230703051449.191259-1-lingyu.liu@intel.com>
2023-07-03 5:06 ` qemudev [this message]
2023-07-03 5:10 ` qemudev
2023-07-03 5:16 ` |WARNING| " checkpatch
2023-07-03 5:39 ` |FAILURE| " 0-day Robot
2023-07-03 17:45 |SUCCESS| " dpdklab
2023-07-03 17:52 dpdklab
2023-07-03 17:52 dpdklab
2023-07-03 17:53 dpdklab
2023-07-03 17:53 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:54 dpdklab
2023-07-03 17:59 dpdklab
2023-07-03 18:00 dpdklab
2023-07-03 18:13 dpdklab
2023-07-03 18:14 dpdklab
2023-07-03 18:15 dpdklab
2023-07-03 18:16 dpdklab
2023-07-03 18:17 dpdklab
2023-07-03 18:17 dpdklab
2023-07-03 18:52 dpdklab
2023-07-03 18:57 dpdklab
2023-07-03 18:58 dpdklab
2023-07-03 19:03 dpdklab
2023-07-03 20:28 dpdklab
2023-07-03 20:31 dpdklab
2023-07-03 21:11 dpdklab
2023-07-04 0:40 dpdklab
2023-07-04 0:45 dpdklab
2023-07-04 1:02 dpdklab
2023-07-04 1:35 dpdklab
2023-07-04 1:39 dpdklab
2023-07-04 17:15 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=202307030506.36356Ce63049268@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).