From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw134257 [PATCH] vfio: add get device info API
Date: Tue, 14 Nov 2023 18:43:13 +0800 [thread overview]
Message-ID: <202311141043.3AEAhDYQ2901669@localhost.localdomain> (raw)
In-Reply-To: <20231114104816.527818-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/134257
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tue, 14 Nov 2023 10:48:16 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fdee0f1b30ae8dfc431465878aae5295372cca6f
134257 --> 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-11-14 11:04 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231114104816.527818-1-mingjinx.ye@intel.com>
2023-11-14 10:43 ` qemudev [this message]
2023-11-14 10:47 ` qemudev
2023-11-14 11:03 ` |WARNING| " checkpatch
2023-11-14 11:59 ` |SUCCESS| " 0-day Robot
2023-11-14 13:32 dpdklab
2023-11-14 13:33 dpdklab
2023-11-14 13:34 dpdklab
2023-11-14 13:36 dpdklab
2023-11-14 13:40 dpdklab
2023-11-14 13:41 dpdklab
2023-11-14 13:41 dpdklab
2023-11-14 13:41 dpdklab
2023-11-14 13:42 dpdklab
2023-11-14 13:42 dpdklab
2023-11-14 13:43 dpdklab
2023-11-14 13:44 dpdklab
2023-11-14 13:44 dpdklab
2023-11-14 13:44 dpdklab
2023-11-14 13:44 dpdklab
2023-11-14 13:45 dpdklab
2023-11-14 13:45 dpdklab
2023-11-14 13:45 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:46 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:47 dpdklab
2023-11-14 13:48 dpdklab
2023-11-14 13:48 dpdklab
2023-11-14 13:48 dpdklab
2023-11-14 13:48 dpdklab
2023-11-14 13:48 dpdklab
2023-11-14 13:49 dpdklab
2023-11-14 13:49 dpdklab
2023-11-14 13:49 dpdklab
2023-11-14 13:49 dpdklab
2023-11-14 13:50 dpdklab
2023-11-14 13:50 dpdklab
2023-11-14 13:50 dpdklab
2023-11-14 13:50 dpdklab
2023-11-14 13:50 dpdklab
2023-11-14 13:51 dpdklab
2023-11-14 13:51 dpdklab
2023-11-14 13:52 dpdklab
2023-11-14 13:52 dpdklab
2023-11-14 14:14 dpdklab
2023-11-14 14:18 dpdklab
2023-11-14 14:18 dpdklab
2023-11-14 14:25 dpdklab
2023-11-14 14:49 dpdklab
2023-11-16 7:33 dpdklab
2023-11-16 7:52 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=202311141043.3AEAhDYQ2901669@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).