From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138922-138936 [PATCH v2 15/15] examples: pack structures when building with MSVC
Date: Thu, 28 Mar 2024 06:48:54 +0800 [thread overview]
Message-ID: <202403272248.42RMmse53936600@localhost.localdomain> (raw)
In-Reply-To: <1711580958-20808-16-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138936
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 27 Mar 2024 16:09:04 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: c29202f2f70abd22e3d74e0671ec9f6cb9e387ee
138922-138936 --> 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-27 23:14 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1711580958-20808-16-git-send-email-roretzla@linux.microsoft.com>
2024-03-27 22:48 ` qemudev [this message]
2024-03-27 22:53 ` qemudev
2024-03-27 23:11 ` |SUCCESS| pw138936 " checkpatch
2024-03-28 0:05 ` 0-day Robot
2024-03-28 13:53 ` |SUCCESS| pw138922-138936 [PATCH] [v2,15/15] examples: pack structur dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:53 ` dpdklab
2024-03-28 13:54 ` dpdklab
2024-03-28 13:55 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 13:56 ` dpdklab
2024-03-28 14:01 ` dpdklab
2024-03-28 14:02 ` dpdklab
2024-03-28 14:06 ` dpdklab
2024-03-28 14:07 ` dpdklab
2024-03-28 14:11 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:29 ` dpdklab
2024-03-28 14:34 ` dpdklab
2024-03-28 14:35 ` dpdklab
2024-03-28 14:37 ` dpdklab
2024-03-28 14:38 ` dpdklab
2024-03-28 14:49 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:53 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:54 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:55 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:56 ` dpdklab
2024-03-28 14:58 ` dpdklab
2024-03-28 14:59 ` dpdklab
2024-03-28 15:02 ` dpdklab
2024-03-28 15:04 ` dpdklab
2024-03-28 15:06 ` dpdklab
2024-03-28 15:08 ` dpdklab
2024-03-28 15:10 ` dpdklab
2024-03-28 15:10 ` dpdklab
2024-03-28 15:11 ` dpdklab
2024-03-28 15:12 ` dpdklab
2024-03-28 15:13 ` dpdklab
2024-03-28 15:14 ` dpdklab
2024-03-28 15:16 ` dpdklab
2024-03-28 15:17 ` dpdklab
2024-03-28 15:17 ` dpdklab
2024-03-28 15:18 ` dpdklab
2024-03-28 15:25 ` dpdklab
2024-03-28 15:26 ` dpdklab
2024-03-28 15:27 ` dpdklab
2024-03-28 15:27 ` dpdklab
2024-03-28 15:29 ` dpdklab
2024-03-28 15:30 ` dpdklab
2024-03-28 15:31 ` dpdklab
2024-03-28 15:33 ` dpdklab
2024-03-28 15:36 ` dpdklab
2024-03-28 15:36 ` dpdklab
2024-03-28 15:37 ` dpdklab
2024-03-28 15:37 ` dpdklab
2024-03-28 15:38 ` dpdklab
2024-03-28 15:38 ` dpdklab
2024-03-28 15:39 ` dpdklab
2024-03-28 15:40 ` dpdklab
2024-03-28 15:42 ` dpdklab
2024-03-28 15:45 ` dpdklab
2024-03-28 15:46 ` dpdklab
2024-03-28 15:46 ` dpdklab
2024-03-28 15:51 ` dpdklab
2024-03-28 15:53 ` dpdklab
2024-03-28 15:54 ` dpdklab
2024-03-28 15:54 ` dpdklab
2024-03-28 15:55 ` dpdklab
2024-03-28 15:56 ` dpdklab
2024-03-28 15:59 ` dpdklab
2024-03-28 16:06 ` dpdklab
2024-03-28 16:17 ` dpdklab
2024-03-28 17:16 ` dpdklab
2024-03-28 17:37 ` dpdklab
2024-03-28 17:49 ` dpdklab
2024-03-28 17:57 ` dpdklab
2024-03-28 18:04 ` dpdklab
2024-04-02 16:10 ` dpdklab
2024-04-02 16:14 ` dpdklab
2024-04-02 16:18 ` dpdklab
2024-04-02 16:22 ` dpdklab
2024-04-02 16:41 ` 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=202403272248.42RMmse53936600@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).