From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126185-126199 [PATCH v7 14/14] eal: do not define typeof macro when building with MSVC
Date: Tue, 18 Apr 2023 00:02:31 +0800 [thread overview]
Message-ID: <202304171602.33HG2VoO2265399@localhost.localdomain> (raw)
In-Reply-To: <1681747838-12778-15-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126199
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 17 Apr 2023 09:10:25 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126185-126199 --> 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-04-17 16:16 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1681747838-12778-15-git-send-email-roretzla@linux.microsoft.com>
2023-04-17 16:02 ` qemudev [this message]
2023-04-17 16:06 ` qemudev
2023-04-17 16:13 ` |SUCCESS| pw126199 " checkpatch
2023-04-17 17:19 ` 0-day Robot
2023-04-17 18:40 |SUCCESS| pw126185-126199 [PATCH] [v7, " dpdklab
2023-04-17 18:45 dpdklab
2023-04-17 18:47 dpdklab
2023-04-17 18:48 dpdklab
2023-04-17 18:49 dpdklab
2023-04-17 18:59 dpdklab
2023-04-17 19:00 dpdklab
2023-04-17 19:03 dpdklab
2023-04-17 19:05 dpdklab
2023-04-17 19:06 dpdklab
2023-04-17 19:08 dpdklab
2023-04-17 19:18 dpdklab
2023-04-17 19:25 dpdklab
2023-04-17 19:27 dpdklab
2023-04-17 19:30 dpdklab
2023-04-17 19:31 dpdklab
2023-04-17 19:31 dpdklab
2023-04-17 19:34 dpdklab
2023-04-17 19:36 dpdklab
2023-04-17 19:38 dpdklab
2023-04-17 19:43 dpdklab
2023-04-17 19:43 dpdklab
2023-04-17 19:45 dpdklab
2023-04-17 19:47 dpdklab
2023-04-17 19:51 dpdklab
2023-04-17 19:58 dpdklab
2023-04-17 20:22 dpdklab
2023-04-17 20:26 dpdklab
2023-04-17 20:28 dpdklab
2023-04-17 20:28 dpdklab
2023-04-17 20:30 dpdklab
2023-04-17 20:31 dpdklab
2023-04-17 20:32 dpdklab
2023-04-17 20:32 dpdklab
2023-04-17 20:49 dpdklab
2023-04-17 21:15 dpdklab
2023-04-17 21:15 dpdklab
2023-04-17 21:17 dpdklab
2023-04-17 21:18 dpdklab
2023-04-17 21:20 dpdklab
2023-04-17 21:32 dpdklab
2023-04-17 21:36 dpdklab
2023-04-17 21:41 dpdklab
2023-04-17 21:49 dpdklab
2023-04-17 21:51 dpdklab
2023-04-17 21:54 dpdklab
2023-04-17 22:33 dpdklab
2023-04-18 3:25 dpdklab
2023-04-18 3:51 dpdklab
2023-04-18 3:51 dpdklab
2023-04-18 3:52 dpdklab
2023-04-18 4:13 dpdklab
2023-04-18 4:13 dpdklab
2023-04-18 5:46 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=202304171602.33HG2VoO2265399@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).