From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw136121-136129 [PATCH 9/9] security: use C11 alignof
Date: Thu, 25 Jan 2024 06:56:22 +0800 [thread overview]
Message-ID: <202401242256.40OMuMEq2949618@localhost.localdomain> (raw)
In-Reply-To: <1706138276-28224-10-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/136129
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 24 Jan 2024 15:17:48 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 2ecc673e5e9a19850ba76d6a976596890f2dade1
136121-136129 --> 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-01-24 23:21 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1706138276-28224-10-git-send-email-roretzla@linux.microsoft.com>
2024-01-24 22:56 ` qemudev [this message]
2024-01-24 23:00 ` qemudev
2024-01-24 23:19 ` |SUCCESS| pw136129 " checkpatch
2024-01-25 0:24 ` 0-day Robot
2024-01-25 1:08 |SUCCESS| pw136121-136129 [PATCH] [9/9] " dpdklab
2024-01-25 1:08 dpdklab
2024-01-25 1:08 dpdklab
2024-01-25 1:10 dpdklab
2024-01-25 1:12 dpdklab
2024-01-25 1:14 dpdklab
2024-01-25 1:16 dpdklab
2024-01-25 1:19 dpdklab
2024-01-25 1:19 dpdklab
2024-01-25 1:22 dpdklab
2024-01-25 1:33 dpdklab
2024-01-25 1:36 dpdklab
2024-01-25 1:36 dpdklab
2024-01-25 1:40 dpdklab
2024-01-25 1:41 dpdklab
2024-01-25 1:42 dpdklab
2024-01-25 1:43 dpdklab
2024-01-25 1:55 dpdklab
2024-01-25 1:56 dpdklab
2024-01-25 1:56 dpdklab
2024-01-25 1:56 dpdklab
2024-01-25 1:59 dpdklab
2024-01-25 1:59 dpdklab
2024-01-25 2:01 dpdklab
2024-01-25 2:02 dpdklab
2024-01-25 2:04 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:05 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:06 dpdklab
2024-01-25 2:07 dpdklab
2024-01-25 2:07 dpdklab
2024-01-25 2:08 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:09 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:10 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:11 dpdklab
2024-01-25 2:12 dpdklab
2024-01-25 2:12 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:13 dpdklab
2024-01-25 2:15 dpdklab
2024-01-25 2:15 dpdklab
2024-01-25 2:17 dpdklab
2024-01-25 2:19 dpdklab
2024-01-25 2:19 dpdklab
2024-01-25 2:23 dpdklab
2024-01-25 2:24 dpdklab
2024-01-25 2:57 dpdklab
2024-01-25 3:32 dpdklab
2024-01-25 4:48 dpdklab
2024-01-25 5:41 dpdklab
2024-01-26 17:13 dpdklab
2024-01-26 17:14 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=202401242256.40OMuMEq2949618@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).