From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143037-143041 [PATCH 5/5] eal: extend bitops to handle volatile pointers
Date: Fri, 9 Aug 2024 16:48:22 +0800 [thread overview]
Message-ID: <202408090848.4798mMsv3805985@localhost.localdomain> (raw)
In-Reply-To: <20240809090439.589295-6-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143041
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Fri, 9 Aug 2024 11:04:35 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143037-143041 --> 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-08-09 9:17 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240809090439.589295-6-mattias.ronnblom@ericsson.com>
2024-08-09 8:48 ` qemudev [this message]
2024-08-09 8:52 ` qemudev
2024-08-09 9:15 ` |WARNING| pw143041 " checkpatch
2024-08-09 10:02 ` |FAILURE| " 0-day Robot
2024-08-09 10:57 ` |SUCCESS| pw143037-143041 [PATCH] [5/5] eal: extend bitops to handle dpdklab
2024-08-09 11:08 ` |PENDING| " dpdklab
2024-08-09 11:09 ` dpdklab
2024-08-09 11:21 ` |SUCCESS| " dpdklab
2024-08-09 11:22 ` dpdklab
2024-08-09 11:24 ` dpdklab
2024-08-09 11:35 ` dpdklab
2024-08-09 11:36 ` dpdklab
2024-08-09 11:43 ` dpdklab
2024-08-09 11:44 ` dpdklab
2024-08-09 11:59 ` dpdklab
2024-08-09 12:18 ` dpdklab
2024-08-09 13:04 ` dpdklab
2024-08-09 13:09 ` dpdklab
2024-08-09 13:14 ` dpdklab
2024-08-09 13:20 ` dpdklab
2024-08-09 13:40 ` dpdklab
2024-08-09 14:01 ` |WARNING| " dpdklab
2024-08-09 14:04 ` dpdklab
2024-08-09 14:05 ` dpdklab
2024-08-09 14:06 ` dpdklab
2024-08-09 14:08 ` dpdklab
2024-08-09 14:09 ` dpdklab
2024-08-09 14:11 ` dpdklab
2024-08-09 14:15 ` dpdklab
2024-08-09 14:16 ` dpdklab
2024-08-09 14:18 ` dpdklab
2024-08-09 14:19 ` dpdklab
2024-08-09 14:22 ` dpdklab
2024-08-09 14:24 ` dpdklab
2024-08-09 16:47 ` |FAILURE| " dpdklab
2024-08-09 16:48 ` dpdklab
2024-08-09 17:52 ` dpdklab
2024-08-09 17:56 ` dpdklab
2024-08-09 18:09 ` dpdklab
2024-08-09 18:11 ` dpdklab
2024-08-09 18:17 ` dpdklab
2024-08-09 18:28 ` dpdklab
2024-08-09 18:39 ` dpdklab
2024-08-09 18:41 ` dpdklab
2024-08-09 18:45 ` dpdklab
2024-08-09 18:46 ` dpdklab
2024-08-09 18:47 ` dpdklab
2024-08-09 18:50 ` dpdklab
2024-08-09 18:53 ` dpdklab
2024-08-09 18:57 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:02 ` dpdklab
2024-08-09 19:04 ` dpdklab
2024-08-09 19:05 ` dpdklab
2024-08-09 19:06 ` dpdklab
2024-08-09 19:06 ` dpdklab
2024-08-09 19:07 ` dpdklab
2024-08-09 19:07 ` dpdklab
2024-08-09 19:08 ` dpdklab
2024-08-09 19:09 ` dpdklab
2024-08-09 19:09 ` dpdklab
2024-08-09 19:10 ` dpdklab
2024-08-09 19:10 ` dpdklab
2024-08-09 19:12 ` dpdklab
2024-08-09 19:22 ` dpdklab
2024-08-09 19:25 ` dpdklab
2024-08-09 19:26 ` dpdklab
2024-08-09 19:27 ` dpdklab
2024-08-09 19:34 ` dpdklab
2024-08-09 19:40 ` dpdklab
2024-08-09 19:41 ` dpdklab
2024-08-09 19:41 ` dpdklab
2024-08-09 19:44 ` dpdklab
2024-08-09 19:54 ` dpdklab
2024-08-09 20:10 ` dpdklab
2024-08-09 20:11 ` dpdklab
2024-08-09 20:12 ` dpdklab
2024-08-09 20:17 ` dpdklab
2024-08-09 20:25 ` dpdklab
2024-08-09 20:32 ` dpdklab
2024-08-09 20:33 ` dpdklab
2024-08-09 20:33 ` dpdklab
2024-08-09 20:38 ` dpdklab
2024-08-09 20:41 ` dpdklab
2024-08-09 21:05 ` dpdklab
2024-08-09 21:15 ` dpdklab
2024-08-10 2:08 ` |WARNING| " 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=202408090848.4798mMsv3805985@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).