From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw122313-122316 [PATCH v4 3/3] ethdev: add standby flags for live migration
Date: Wed, 18 Jan 2023 23:47:01 +0800 [thread overview]
Message-ID: <202301181547.30IFl1jJ2350569@localhost.localdomain> (raw)
In-Reply-To: <20230118154447.595231-4-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/122316
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Wed, 18 Jan 2023 17:44:44 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 8b0a1b8cb4818921c7b57b9a656154ccb7ed69db
122313-122316 --> 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:[~2023-01-18 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230118154447.595231-4-rongweil@nvidia.com>
2023-01-18 15:46 ` |SUCCESS| pw122316 " checkpatch
2023-01-18 15:47 ` qemudev [this message]
2023-01-18 15:50 ` |SUCCESS| pw122313-122316 " qemudev
2023-01-18 16:59 ` |SUCCESS| pw122316 " 0-day Robot
2023-01-18 16:10 |SUCCESS| pw122313-122316 [PATCH] [v4, " dpdklab
2023-01-18 16:15 dpdklab
2023-01-18 16:15 dpdklab
2023-01-18 16:17 dpdklab
2023-01-18 16:17 dpdklab
2023-01-18 16:19 dpdklab
2023-01-18 16:20 dpdklab
2023-01-18 16:22 dpdklab
2023-01-18 16:25 dpdklab
2023-01-18 16:26 dpdklab
2023-01-18 16:30 dpdklab
2023-01-18 16:32 dpdklab
2023-01-18 16:46 dpdklab
2023-01-19 5:40 dpdklab
2023-01-19 5:54 dpdklab
2023-01-19 5:54 dpdklab
2023-01-19 5:54 dpdklab
2023-01-19 5:55 dpdklab
2023-01-19 5:55 dpdklab
2023-01-19 5:55 dpdklab
2023-01-19 5:55 dpdklab
2023-01-19 7:03 dpdklab
2023-01-21 4:20 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=202301181547.30IFl1jJ2350569@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).