From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125220 [PATCH v1] bus/ifpga: add fpga bus cleanup
Date: Fri, 17 Mar 2023 09:50:52 +0800 [thread overview]
Message-ID: <202303170150.32H1oqOC1038821@localhost.localdomain> (raw)
In-Reply-To: <20230316204434.360283-1-wei.huang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125220
_Compilation OK_
Submitter: Wei Huang <wei.huang@intel.com>
Date: Thu, 16 Mar 2023 16:44:34 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823
125220 --> 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-03-17 2:05 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316204434.360283-1-wei.huang@intel.com>
2023-03-17 1:45 ` checkpatch
2023-03-17 1:50 ` qemudev [this message]
2023-03-17 1:54 ` qemudev
2023-03-17 3:31 |SUCCESS| pw125220 [PATCH] [v1] " dpdklab
2023-03-17 3:43 dpdklab
2023-03-17 3:44 dpdklab
2023-03-17 3:44 dpdklab
2023-03-17 3:47 dpdklab
2023-03-17 3:54 dpdklab
2023-03-17 3:58 dpdklab
2023-03-17 3:59 dpdklab
2023-03-17 4:04 dpdklab
2023-03-17 4:08 dpdklab
2023-03-17 4:13 dpdklab
2023-03-17 4:27 dpdklab
2023-03-17 4:28 dpdklab
2023-03-17 4:34 dpdklab
2023-03-17 4:39 dpdklab
2023-03-17 4:41 dpdklab
2023-03-17 4:52 dpdklab
2023-03-17 5:09 dpdklab
2023-03-17 5:12 dpdklab
2023-03-17 6:01 dpdklab
2023-03-17 6:04 dpdklab
2023-03-17 6:22 dpdklab
2023-03-17 6:43 dpdklab
2023-03-17 6:55 dpdklab
2023-03-17 8:20 dpdklab
2023-03-17 8:26 dpdklab
2023-03-17 14:42 dpdklab
2023-03-19 5:27 dpdklab
2023-03-19 7:08 dpdklab
2023-03-19 11:59 dpdklab
2023-03-19 12:56 dpdklab
2023-03-19 22:00 dpdklab
2023-03-19 22:24 dpdklab
2023-03-19 22:25 dpdklab
2023-03-19 22:25 dpdklab
2023-03-19 22:31 dpdklab
2023-03-19 22:36 dpdklab
2023-03-19 22:43 dpdklab
2023-03-19 22:44 dpdklab
2023-03-19 22:49 dpdklab
2023-03-19 22:53 dpdklab
2023-03-19 23:02 dpdklab
2023-03-19 23:04 dpdklab
2023-03-19 23:05 dpdklab
2023-03-19 23:06 dpdklab
2023-03-20 0:02 dpdklab
2023-03-20 0:15 dpdklab
2023-03-20 0:19 dpdklab
2023-03-20 0:20 dpdklab
2023-03-20 0:22 dpdklab
2023-03-20 0:33 dpdklab
2023-03-20 0:34 dpdklab
2023-03-20 0:36 dpdklab
2023-03-20 0:42 dpdklab
2023-03-20 0:47 dpdklab
2023-03-20 0:50 dpdklab
2023-03-20 0:53 dpdklab
2023-03-20 0:59 dpdklab
2023-03-20 0:59 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=202303170150.32H1oqOC1038821@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).