From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124713-124715 [PATCH v3 3/3] net/mlx5: fix Windows build with MinGW GCC 12
Date: Mon, 6 Mar 2023 15:19:43 +0800 [thread overview]
Message-ID: <202303060719.3267Jh393957995@localhost.localdomain> (raw)
In-Reply-To: <20230302132150.3330288-4-thomas@monjalon.net>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124715
_Compilation OK_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thu, 2 Mar 2023 14:21:48 +0100
DPDK git baseline: Repo:dpdk-next-net-mlx
Branch: for-next-net
CommitID: 889996da9454bbdd260c40b4e085498884a760da
124713-124715 --> 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 prev parent reply other threads:[~2023-03-06 7:33 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230302132150.3330288-4-thomas@monjalon.net>
2023-03-02 13:23 ` |WARNING| pw124715 " checkpatch
2023-03-02 15:39 ` |SUCCESS| " 0-day Robot
2023-03-06 7:19 ` qemudev [this message]
2023-03-06 7:20 ` |SUCCESS| pw124713-124715 " qemudev
2023-03-06 3:21 |SUCCESS| pw124713-124715 [PATCH] [v3, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 3:17 dpdklab
2023-03-06 3:06 dpdklab
2023-03-06 3:02 dpdklab
2023-03-06 2:59 dpdklab
2023-03-06 2:47 dpdklab
2023-03-05 13:09 dpdklab
2023-03-05 13:09 dpdklab
2023-03-05 13:07 dpdklab
2023-03-05 13:04 dpdklab
2023-03-05 13:03 dpdklab
2023-03-05 13:01 dpdklab
2023-03-05 13:00 dpdklab
2023-03-05 13:00 dpdklab
2023-03-05 12:58 dpdklab
2023-03-05 12:58 dpdklab
2023-03-05 12:57 dpdklab
2023-03-05 12:55 dpdklab
2023-03-05 12:52 dpdklab
2023-03-05 12:47 dpdklab
2023-03-05 12:47 dpdklab
2023-03-05 12:45 dpdklab
2023-03-05 12:41 dpdklab
2023-03-05 12:38 dpdklab
2023-03-05 12:35 dpdklab
2023-03-05 12:34 dpdklab
2023-03-05 12:32 dpdklab
2023-03-05 12:31 dpdklab
2023-03-05 12:24 dpdklab
2023-03-05 12:22 dpdklab
2023-03-05 12:14 dpdklab
2023-03-05 12:06 dpdklab
2023-03-05 12:05 dpdklab
2023-03-05 11:46 dpdklab
2023-03-04 18:36 dpdklab
2023-03-04 16:35 dpdklab
2023-03-04 13:33 dpdklab
2023-03-04 12:42 dpdklab
2023-03-04 7:43 dpdklab
2023-03-04 6:32 dpdklab
2023-03-03 23:37 dpdklab
2023-03-03 23:07 dpdklab
2023-03-03 23:02 dpdklab
2023-03-03 22:58 dpdklab
2023-03-03 22:54 dpdklab
2023-03-03 22:50 dpdklab
2023-03-03 22:48 dpdklab
2023-03-03 22:47 dpdklab
2023-03-03 22:47 dpdklab
2023-03-03 22:46 dpdklab
2023-03-03 22:42 dpdklab
2023-03-03 22:37 dpdklab
2023-03-03 22:26 dpdklab
2023-03-03 22:14 dpdklab
2023-03-03 22:10 dpdklab
2023-03-03 22:05 dpdklab
2023-03-03 21:58 dpdklab
2023-03-03 21:55 dpdklab
2023-03-03 21:53 dpdklab
2023-03-03 21:52 dpdklab
2023-03-03 21:44 dpdklab
2023-03-03 21:39 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=202303060719.3267Jh393957995@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).