From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121977-121980 [PATCH v2 4/4] net/mlx5: fix Windows build with MinGW GCC 12
Date: Fri, 13 Jan 2023 04:30:35 +0800 [thread overview]
Message-ID: <202301122030.30CKUZ4K3898561@localhost.localdomain> (raw)
In-Reply-To: <20230112203719.1528619-5-thomas@monjalon.net>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121980
_Compilation OK_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Thu, 12 Jan 2023 21:37:15 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 83397b9f073904438965e1fda2efe76f7850fe01
121977-121980 --> 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:[~2023-01-12 20:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230112203719.1528619-5-thomas@monjalon.net>
2023-01-12 20:30 ` qemudev [this message]
2023-01-12 20:34 ` qemudev
2023-01-12 20:39 ` |WARNING| pw121980 " checkpatch
2023-01-12 21:59 ` |SUCCESS| " 0-day Robot
2023-01-12 21:11 |SUCCESS| pw121977-121980 [PATCH] [v2, " dpdklab
2023-01-12 21:12 dpdklab
2023-01-12 21:16 dpdklab
2023-01-12 21:18 dpdklab
2023-01-12 21:20 dpdklab
2023-01-12 21:27 dpdklab
2023-01-12 21:31 dpdklab
2023-01-13 0:51 dpdklab
2023-01-13 10:29 dpdklab
2023-01-13 10:29 dpdklab
2023-01-13 10:29 dpdklab
2023-01-13 10:30 dpdklab
2023-01-13 10:30 dpdklab
2023-01-13 10:30 dpdklab
2023-01-13 10:30 dpdklab
2023-01-13 10:30 dpdklab
2023-01-13 10:31 dpdklab
2023-01-13 10:31 dpdklab
2023-01-13 10:34 dpdklab
2023-01-13 14:20 dpdklab
2023-01-13 19:43 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=202301122030.30CKUZ4K3898561@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).