From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139526-139533 [PATCH v2 8/8] net/nfp: unify port create and destroy interface
Date: Fri, 19 Apr 2024 13:06:07 +0800 [thread overview]
Message-ID: <202404190506.43J567q72100372@localhost.localdomain> (raw)
In-Reply-To: <20240419052349.1294696-9-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139533
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 19 Apr 2024 13:23:42 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: ae59c6a42ee4f49409997765ae64502944e0ac33
139526-139533 --> 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 5:31 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240419052349.1294696-9-chaoyong.he@corigine.com>
2024-04-19 5:06 ` qemudev [this message]
2024-04-19 5:10 ` qemudev
2024-04-19 5:27 ` |SUCCESS| pw139533 " checkpatch
2024-04-19 6:38 ` |SUCCESS| pw139526-139533 [PATCH] [v2,8/8] net/nfp: unify port creat dpdklab
2024-04-19 6:40 ` dpdklab
2024-04-19 6:42 ` dpdklab
2024-04-19 6:46 ` dpdklab
2024-04-19 6:46 ` dpdklab
2024-04-19 7:00 ` dpdklab
2024-04-19 7:01 ` dpdklab
2024-04-19 7:04 ` dpdklab
2024-04-19 7:56 ` dpdklab
2024-04-19 7:57 ` dpdklab
2024-04-19 7:58 ` dpdklab
2024-04-19 8:01 ` dpdklab
2024-04-19 8:02 ` dpdklab
2024-04-19 8:03 ` dpdklab
2024-04-19 8:04 ` dpdklab
2024-04-19 8:05 ` dpdklab
2024-04-19 8:06 ` dpdklab
2024-04-19 8:07 ` dpdklab
2024-04-19 8:07 ` dpdklab
2024-04-19 8:09 ` dpdklab
2024-04-19 8:10 ` dpdklab
2024-04-19 8:10 ` dpdklab
2024-04-19 8:11 ` dpdklab
2024-04-19 8:11 ` dpdklab
2024-04-19 8:12 ` dpdklab
2024-04-19 8:12 ` dpdklab
2024-04-19 8:14 ` dpdklab
2024-04-19 8:16 ` dpdklab
2024-04-19 8:17 ` dpdklab
2024-04-19 8:17 ` dpdklab
2024-04-19 8:17 ` dpdklab
2024-04-19 8:17 ` dpdklab
2024-04-19 8:18 ` dpdklab
2024-04-19 8:18 ` dpdklab
2024-04-19 8:18 ` dpdklab
2024-04-19 8:19 ` dpdklab
2024-04-19 8:25 ` dpdklab
2024-04-19 8:31 ` dpdklab
2024-04-19 8:32 ` dpdklab
2024-04-19 8:33 ` dpdklab
2024-04-19 8:33 ` dpdklab
2024-04-19 8:33 ` dpdklab
2024-04-19 8:35 ` dpdklab
2024-04-19 8:35 ` dpdklab
2024-04-19 8:36 ` dpdklab
2024-04-19 8:37 ` dpdklab
2024-04-19 8:39 ` dpdklab
2024-04-19 8:40 ` dpdklab
2024-04-19 8:42 ` dpdklab
2024-04-19 8:42 ` dpdklab
2024-04-19 8:42 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:43 ` dpdklab
2024-04-19 8:44 ` dpdklab
2024-04-19 8:44 ` dpdklab
2024-04-19 8:44 ` dpdklab
2024-04-19 8:44 ` dpdklab
2024-04-19 8:45 ` dpdklab
2024-04-19 8:45 ` dpdklab
2024-04-19 8:45 ` dpdklab
2024-04-19 8:47 ` dpdklab
2024-04-19 8:50 ` dpdklab
2024-04-19 8:50 ` dpdklab
2024-04-19 8:51 ` dpdklab
2024-04-19 8:51 ` dpdklab
2024-04-19 8:55 ` dpdklab
2024-04-19 8:55 ` dpdklab
2024-04-19 8:55 ` dpdklab
2024-04-19 9:13 ` dpdklab
2024-04-19 9:14 ` dpdklab
2024-04-19 9:22 ` dpdklab
2024-04-19 9:29 ` dpdklab
2024-04-19 9:29 ` dpdklab
2024-04-19 9:44 ` dpdklab
2024-04-19 10:09 ` dpdklab
2024-04-19 10:26 ` dpdklab
2024-04-19 11:50 ` 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=202404190506.43J567q72100372@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).