From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139516-139523 [PATCH 8/8] net/nfp: unify port create and destroy interface
Date: Fri, 19 Apr 2024 10:51:47 +0800 [thread overview]
Message-ID: <202404190251.43J2pliv1971360@localhost.localdomain> (raw)
In-Reply-To: <20240419031226.1191069-9-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139523
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 19 Apr 2024 11:12:19 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: ae59c6a42ee4f49409997765ae64502944e0ac33
139516-139523 --> 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:[~2024-04-19 3:16 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419031226.1191069-9-chaoyong.he@corigine.com>
2024-04-19 2:51 ` qemudev [this message]
2024-04-19 2:56 ` qemudev
2024-04-19 3:14 ` |SUCCESS| pw139523 " checkpatch
2024-04-19 4:11 ` |SUCCESS| pw139516-139523 [PATCH] [8/8] net/nfp: unify port create a dpdklab
2024-04-19 4:12 ` dpdklab
2024-04-19 4:12 ` dpdklab
2024-04-19 4:12 ` dpdklab
2024-04-19 4:12 ` dpdklab
2024-04-19 4:13 ` dpdklab
2024-04-19 4:13 ` dpdklab
2024-04-19 4:13 ` dpdklab
2024-04-19 4:13 ` dpdklab
2024-04-19 4:13 ` dpdklab
2024-04-19 4:14 ` dpdklab
2024-04-19 4:14 ` dpdklab
2024-04-19 4:15 ` dpdklab
2024-04-19 4:15 ` dpdklab
2024-04-19 4:15 ` dpdklab
2024-04-19 4:15 ` dpdklab
2024-04-19 4:16 ` dpdklab
2024-04-19 4:16 ` dpdklab
2024-04-19 4:16 ` dpdklab
2024-04-19 4:16 ` dpdklab
2024-04-19 4:16 ` dpdklab
2024-04-19 4:17 ` dpdklab
2024-04-19 4:17 ` dpdklab
2024-04-19 4:17 ` dpdklab
2024-04-19 4:17 ` dpdklab
2024-04-19 4:18 ` dpdklab
2024-04-19 4:18 ` dpdklab
2024-04-19 4:18 ` dpdklab
2024-04-19 4:18 ` dpdklab
2024-04-19 4:19 ` dpdklab
2024-04-19 4:19 ` dpdklab
2024-04-19 4:19 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:20 ` dpdklab
2024-04-19 4:21 ` dpdklab
2024-04-19 4:23 ` dpdklab
2024-04-19 4:24 ` dpdklab
2024-04-19 4:24 ` dpdklab
2024-04-19 4:26 ` dpdklab
2024-04-19 4:26 ` dpdklab
2024-04-19 4:26 ` dpdklab
2024-04-19 4:27 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:28 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:29 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:30 ` dpdklab
2024-04-19 4:31 ` dpdklab
2024-04-19 4:31 ` dpdklab
2024-04-19 4:31 ` dpdklab
2024-04-19 4:31 ` dpdklab
2024-04-19 4:31 ` dpdklab
2024-04-19 4:32 ` dpdklab
2024-04-19 4:58 ` dpdklab
2024-04-19 4:59 ` dpdklab
2024-04-19 5:19 ` dpdklab
2024-04-19 5:21 ` dpdklab
2024-04-19 5:31 ` dpdklab
2024-04-19 5:34 ` dpdklab
2024-04-19 5:41 ` dpdklab
2024-04-19 5:59 ` dpdklab
2024-04-19 6:00 ` dpdklab
2024-04-19 6:01 ` 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=202404190251.43J2pliv1971360@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).