From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125745 [PATCH v2] devtools: stop compiler atomics with no C11 equivalent
Date: Tue, 4 Apr 2023 08:12:05 +0800 [thread overview]
Message-ID: <202304040012.3340C5DE858659@localhost.localdomain> (raw)
In-Reply-To: <1680567698-7874-1-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125745
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Mon, 3 Apr 2023 17:21:38 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 189c02f5ec891ed02927062e124e8ca03adf74e7
125745 --> 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-04 0:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1680567698-7874-1-git-send-email-roretzla@linux.microsoft.com>
2023-04-04 0:12 ` qemudev [this message]
2023-04-04 0:16 ` qemudev
2023-04-04 0:23 ` checkpatch
2023-04-04 1:18 ` 0-day Robot
2023-04-06 4:34 |SUCCESS| pw125745 [PATCH] [v2] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-04-06 4:24 dpdklab
2023-04-06 4:17 dpdklab
2023-04-06 4:17 dpdklab
2023-04-06 4:16 dpdklab
2023-04-06 4:15 dpdklab
2023-04-06 4:15 dpdklab
2023-04-06 4:13 dpdklab
2023-04-06 4:11 dpdklab
2023-04-06 4:11 dpdklab
2023-04-06 4:06 dpdklab
2023-04-06 4:05 dpdklab
2023-04-06 4:04 dpdklab
2023-04-06 3:57 dpdklab
2023-04-06 3:54 dpdklab
2023-04-06 3:51 dpdklab
2023-04-06 3:36 dpdklab
2023-04-04 2:39 dpdklab
2023-04-04 2:38 dpdklab
2023-04-04 2:32 dpdklab
2023-04-04 2:31 dpdklab
2023-04-04 2:24 dpdklab
2023-04-04 2:21 dpdklab
2023-04-04 2:21 dpdklab
2023-04-04 2:15 dpdklab
2023-04-04 2:14 dpdklab
2023-04-04 2:13 dpdklab
2023-04-04 2:10 dpdklab
2023-04-04 2:03 dpdklab
2023-04-04 2:01 dpdklab
2023-04-04 1:57 dpdklab
2023-04-04 1:57 dpdklab
2023-04-04 1:57 dpdklab
2023-04-04 1:52 dpdklab
2023-04-04 1:46 dpdklab
2023-04-04 1:46 dpdklab
2023-04-04 1:42 dpdklab
2023-04-04 1:41 dpdklab
2023-04-04 1:40 dpdklab
2023-04-04 1:40 dpdklab
2023-04-04 1:39 dpdklab
2023-04-04 1:37 dpdklab
2023-04-04 1:35 dpdklab
2023-04-04 1:35 dpdklab
2023-04-04 1:33 dpdklab
2023-04-04 1:30 dpdklab
2023-04-04 1:30 dpdklab
2023-04-04 1:26 dpdklab
2023-04-04 1:24 dpdklab
2023-04-04 1:23 dpdklab
2023-04-04 1:21 dpdklab
2023-04-04 1:19 dpdklab
2023-04-04 1:18 dpdklab
2023-04-04 1: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=202304040012.3340C5DE858659@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).