From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144115-144112 [PATCH v8 6/6] eal: extend bitops to handle volatile pointers
Date: Tue, 17 Sep 2024 18:31:57 +0800 [thread overview]
Message-ID: <202409171031.48HAVvNr2030252@localhost.localdomain> (raw)
In-Reply-To: <20240917104811.723863-7-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144112
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Tue, 17 Sep 2024 12:48:06 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144115-144112 --> 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-09-17 11:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240917104811.723863-7-mattias.ronnblom@ericsson.com>
2024-09-17 10:31 ` qemudev [this message]
2024-09-17 10:36 ` qemudev
2024-09-17 10:59 ` |WARNING| pw144112 " checkpatch
2024-09-17 12:04 ` |FAILURE| " 0-day Robot
2024-09-17 14:24 ` |SUCCESS| pw144115-144112 [PATCH] [v8,6/6] eal: extend bitops to han dpdklab
2024-09-17 15:18 ` dpdklab
2024-09-17 15:33 ` dpdklab
2024-09-17 15:46 ` dpdklab
2024-09-17 17:06 ` dpdklab
2024-09-17 17:29 ` dpdklab
2024-09-17 17:31 ` dpdklab
2024-09-17 18:07 ` dpdklab
2024-09-17 18:29 ` dpdklab
2024-09-17 18:31 ` dpdklab
2024-09-17 18:35 ` dpdklab
2024-09-17 18:47 ` dpdklab
2024-09-17 18:53 ` |FAILURE| " dpdklab
2024-09-17 18:54 ` |PENDING| " dpdklab
2024-09-17 18:59 ` dpdklab
2024-09-17 19:00 ` |FAILURE| " dpdklab
2024-09-17 19:01 ` |SUCCESS| " dpdklab
2024-09-17 19:01 ` |FAILURE| " dpdklab
2024-09-17 19:05 ` |SUCCESS| " dpdklab
2024-09-17 19:24 ` |PENDING| " dpdklab
2024-09-17 20:00 ` |FAILURE| " dpdklab
2024-09-17 20:03 ` |PENDING| " dpdklab
2024-09-17 20:17 ` dpdklab
2024-09-17 20:40 ` |SUCCESS| " dpdklab
2024-09-17 21:16 ` |FAILURE| " dpdklab
2024-09-17 21:18 ` dpdklab
2024-09-17 21:42 ` |SUCCESS| " dpdklab
2024-09-17 21:43 ` dpdklab
2024-09-17 21:44 ` dpdklab
2024-09-17 22:19 ` dpdklab
2024-09-17 23:24 ` dpdklab
2024-09-17 23:27 ` dpdklab
2024-09-17 23:32 ` dpdklab
2024-09-18 1:40 ` dpdklab
2024-09-18 2:16 ` dpdklab
2024-09-22 6:10 ` dpdklab
2024-09-22 6:22 ` dpdklab
2024-09-22 6:40 ` dpdklab
2024-09-22 6:52 ` 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=202409171031.48HAVvNr2030252@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).