From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139116 [PATCH] meson/mlx5: Suppress -Wunused-value diagnostic
Date: Fri, 5 Apr 2024 18:52:38 +0800 [thread overview]
Message-ID: <202404051052.435Aqcg62675529@localhost.localdomain> (raw)
In-Reply-To: <20240405111310.3280084-1-sebastian.brzezinka@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139116
_Compilation OK_
Submitter: Sebastian Brzezinka <sebastian.brzezinka@intel.com>
Date: Fri, 5 Apr 2024 13:13:10 +0200
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
139116 --> 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-05 11:17 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240405111310.3280084-1-sebastian.brzezinka@intel.com>
2024-04-05 10:52 ` qemudev [this message]
2024-04-05 10:56 ` qemudev
2024-04-05 11:14 ` |WARNING| " checkpatch
2024-04-05 12:03 ` |SUCCESS| pw139116 [PATCH] meson/mlx5: Suppress -Wunused-value diagn dpdklab
2024-04-05 12:04 ` dpdklab
2024-04-05 12:05 ` dpdklab
2024-04-05 12:05 ` dpdklab
2024-04-05 12:06 ` dpdklab
2024-04-05 12:07 ` dpdklab
2024-04-05 12:08 ` dpdklab
2024-04-05 12:09 ` dpdklab
2024-04-05 12:09 ` dpdklab
2024-04-05 12:10 ` dpdklab
2024-04-05 12:10 ` dpdklab
2024-04-05 12:13 ` dpdklab
2024-04-05 12:17 ` dpdklab
2024-04-05 12:18 ` dpdklab
2024-04-05 12:18 ` dpdklab
2024-04-05 12:19 ` dpdklab
2024-04-05 12:19 ` dpdklab
2024-04-05 12:19 ` dpdklab
2024-04-05 12:20 ` dpdklab
2024-04-05 12:20 ` dpdklab
2024-04-05 12:21 ` dpdklab
2024-04-05 12:21 ` dpdklab
2024-04-05 12:22 ` dpdklab
2024-04-05 12:22 ` dpdklab
2024-04-05 12:22 ` dpdklab
2024-04-05 12:22 ` dpdklab
2024-04-05 12:22 ` dpdklab
2024-04-05 12:23 ` dpdklab
2024-04-05 12:23 ` dpdklab
2024-04-05 12:24 ` dpdklab
2024-04-05 12:24 ` dpdklab
2024-04-05 12:24 ` dpdklab
2024-04-05 12:24 ` dpdklab
2024-04-05 12:24 ` dpdklab
2024-04-05 12:25 ` dpdklab
2024-04-05 12:25 ` dpdklab
2024-04-05 12:26 ` dpdklab
2024-04-05 12:26 ` dpdklab
2024-04-05 12:26 ` dpdklab
2024-04-05 12:27 ` dpdklab
2024-04-05 12:28 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:29 ` dpdklab
2024-04-05 12:30 ` dpdklab
2024-04-05 12:31 ` dpdklab
2024-04-05 12:31 ` dpdklab
2024-04-05 12:32 ` dpdklab
2024-04-05 12:32 ` dpdklab
2024-04-05 12:32 ` dpdklab
2024-04-05 12:33 ` dpdklab
2024-04-05 12:33 ` dpdklab
2024-04-05 12:33 ` dpdklab
2024-04-05 12:34 ` dpdklab
2024-04-05 12:34 ` dpdklab
2024-04-05 12:41 ` dpdklab
2024-04-05 12:41 ` dpdklab
2024-04-05 12:43 ` dpdklab
2024-04-05 12:44 ` dpdklab
2024-04-05 12:49 ` dpdklab
2024-04-05 12:49 ` dpdklab
2024-04-05 12:49 ` dpdklab
2024-04-05 12:50 ` dpdklab
2024-04-05 12:51 ` dpdklab
2024-04-05 12:51 ` dpdklab
2024-04-05 12:52 ` dpdklab
2024-04-05 12:52 ` dpdklab
2024-04-05 12:52 ` dpdklab
2024-04-05 12:53 ` dpdklab
2024-04-05 12:54 ` dpdklab
2024-04-05 12:55 ` dpdklab
2024-04-05 12:58 ` dpdklab
2024-04-05 12:58 ` dpdklab
2024-04-05 13:01 ` dpdklab
2024-04-05 13:07 ` dpdklab
2024-04-05 13:11 ` dpdklab
2024-04-05 13:11 ` dpdklab
2024-04-05 13:15 ` dpdklab
2024-04-05 13:26 ` dpdklab
2024-04-05 15:08 ` dpdklab
2024-04-05 15:23 ` 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=202404051052.435Aqcg62675529@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).