From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138108 [PATCH v2] eal/windows: resolve conversion and truncation warnings
Date: Fri, 8 Mar 2024 02:12:04 +0800 [thread overview]
Message-ID: <202403071812.427IC40m514374@localhost.localdomain> (raw)
In-Reply-To: <1709836482-22576-1-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138108
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Thu, 7 Mar 2024 10:34:42 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9468040f094312a9cff5452465ca0b561e0474f4
138108 --> 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-03-07 18:36 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1709836482-22576-1-git-send-email-roretzla@linux.microsoft.com>
2024-03-07 18:12 ` qemudev [this message]
2024-03-07 18:16 ` qemudev
2024-03-07 18:36 ` checkpatch
2024-03-07 19:24 ` 0-day Robot
2024-03-07 19:43 ` |SUCCESS| pw138108 [PATCH] [v2] eal/windows: resolve conversion and dpdklab
2024-03-07 19:43 ` dpdklab
2024-03-07 19:44 ` dpdklab
2024-03-07 19:44 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:45 ` dpdklab
2024-03-07 19:46 ` dpdklab
2024-03-07 19:47 ` dpdklab
2024-03-07 19:47 ` dpdklab
2024-03-07 19:48 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:49 ` dpdklab
2024-03-07 19:50 ` dpdklab
2024-03-07 19:50 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:52 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:53 ` dpdklab
2024-03-07 19:54 ` dpdklab
2024-03-07 19:54 ` dpdklab
2024-03-07 19:55 ` dpdklab
2024-03-07 19:55 ` dpdklab
2024-03-07 19:56 ` dpdklab
2024-03-07 19:56 ` dpdklab
2024-03-07 19:58 ` dpdklab
2024-03-07 19:59 ` dpdklab
2024-03-07 20:00 ` dpdklab
2024-03-07 20:01 ` dpdklab
2024-03-07 20:03 ` dpdklab
2024-03-07 20:03 ` dpdklab
2024-03-07 20:04 ` dpdklab
2024-03-07 20:06 ` dpdklab
2024-03-07 20:06 ` dpdklab
2024-03-07 20:07 ` dpdklab
2024-03-07 20:07 ` dpdklab
2024-03-07 20:08 ` dpdklab
2024-03-07 20:09 ` dpdklab
2024-03-07 20:09 ` |FAILURE| " dpdklab
2024-03-07 20:10 ` |SUCCESS| " dpdklab
2024-03-07 20:10 ` dpdklab
2024-03-07 20:11 ` |FAILURE| " dpdklab
2024-03-07 20:13 ` dpdklab
2024-03-07 20:15 ` dpdklab
2024-03-07 20:17 ` |SUCCESS| " dpdklab
2024-03-07 20:18 ` |FAILURE| " dpdklab
2024-03-07 20:20 ` dpdklab
2024-03-07 21:07 ` |SUCCESS| " dpdklab
2024-03-07 21:36 ` |FAILURE| " dpdklab
2024-03-07 21:47 ` |SUCCESS| " dpdklab
2024-03-07 21:49 ` dpdklab
2024-03-07 21:52 ` dpdklab
2024-03-07 21:56 ` dpdklab
2024-03-07 21:59 ` dpdklab
2024-03-07 22:01 ` dpdklab
2024-03-07 22:06 ` dpdklab
2024-03-07 22:16 ` dpdklab
2024-03-07 22:55 ` dpdklab
2024-03-08 2:28 ` dpdklab
2024-03-08 8:57 ` dpdklab
2024-03-08 8:58 ` dpdklab
2024-03-08 9:00 ` dpdklab
2024-03-08 9:01 ` dpdklab
2024-03-12 7:23 ` dpdklab
2024-03-12 8:24 ` dpdklab
2024-03-12 8:55 ` 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=202403071812.427IC40m514374@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).