From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139380 [PATCH] common/mlx5: fix unsigned signed mismatch warning
Date: Tue, 16 Apr 2024 06:47:08 +0800 [thread overview]
Message-ID: <202404152247.43FMl8wD4130031@localhost.localdomain> (raw)
In-Reply-To: <1713222577-7382-1-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139380
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 15 Apr 2024 16:09:37 -0700
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
139380 --> 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-15 23:12 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1713222577-7382-1-git-send-email-roretzla@linux.microsoft.com>
2024-04-15 22:47 ` qemudev [this message]
2024-04-15 22:51 ` qemudev
2024-04-15 23:10 ` checkpatch
2024-04-15 23:56 ` |SUCCESS| pw139380 [PATCH] common/mlx5: fix unsigned signed mismatch dpdklab
2024-04-15 23:58 ` dpdklab
2024-04-16 0:03 ` dpdklab
2024-04-16 0:04 ` dpdklab
2024-04-16 0:04 ` dpdklab
2024-04-16 0:04 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:05 ` dpdklab
2024-04-16 0:06 ` dpdklab
2024-04-16 0:06 ` dpdklab
2024-04-16 0:06 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:07 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:08 ` dpdklab
2024-04-16 0:09 ` dpdklab
2024-04-16 0:09 ` dpdklab
2024-04-16 0:09 ` dpdklab
2024-04-16 0:10 ` |SUCCESS| pw139380 [PATCH] common/mlx5: fix unsigned signed mismatch warning 0-day Robot
2024-04-16 0:14 ` |SUCCESS| pw139380 [PATCH] common/mlx5: fix unsigned signed mismatch dpdklab
2024-04-16 0:15 ` dpdklab
2024-04-16 0:16 ` dpdklab
2024-04-16 0:19 ` dpdklab
2024-04-16 0:19 ` dpdklab
2024-04-16 0:19 ` dpdklab
2024-04-16 0:19 ` dpdklab
2024-04-16 0:20 ` dpdklab
2024-04-16 0:20 ` dpdklab
2024-04-16 0:20 ` dpdklab
2024-04-16 0:20 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:21 ` dpdklab
2024-04-16 0:22 ` dpdklab
2024-04-16 0:22 ` dpdklab
2024-04-16 0:22 ` dpdklab
2024-04-16 0:22 ` dpdklab
2024-04-16 0:22 ` dpdklab
2024-04-16 0:23 ` dpdklab
2024-04-16 0:23 ` dpdklab
2024-04-16 0:23 ` dpdklab
2024-04-16 0:23 ` dpdklab
2024-04-16 0:27 ` dpdklab
2024-04-16 0:27 ` dpdklab
2024-04-16 0:27 ` dpdklab
2024-04-16 0:29 ` dpdklab
2024-04-16 0:30 ` dpdklab
2024-04-16 0:30 ` dpdklab
2024-04-16 0:30 ` dpdklab
2024-04-16 0:30 ` dpdklab
2024-04-16 0:31 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:33 ` dpdklab
2024-04-16 0:34 ` dpdklab
2024-04-16 0:34 ` dpdklab
2024-04-16 0:34 ` dpdklab
2024-04-16 0:35 ` dpdklab
2024-04-16 0:45 ` dpdklab
2024-04-16 0:45 ` dpdklab
2024-04-16 1:00 ` dpdklab
2024-04-16 1:00 ` dpdklab
2024-04-16 1:01 ` dpdklab
2024-04-16 1:01 ` dpdklab
2024-04-16 1:01 ` dpdklab
2024-04-16 1:17 ` dpdklab
2024-04-16 1:33 ` dpdklab
2024-04-16 1:33 ` 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=202404152247.43FMl8wD4130031@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).