From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140738-140739 [PATCH 5/5] eal: provide option to use compiler memcpy instead of RTE
Date: Wed, 5 Jun 2024 14:34:09 +0800 [thread overview]
Message-ID: <202406050634.4556Y98r3654443@localhost.localdomain> (raw)
In-Reply-To: <20240605064945.369310-6-mattias.ronnblom@ericsson.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140739
_Compilation OK_
Submitter: Mattias Rönnblom <mattias.ronnblom@ericsson.com>
Date: Wed, 5 Jun 2024 08:49:41 +0200
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 76cef1af8bdaeaf67a5c4ca5df3f221df994dc46
140738-140739 --> 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-06-05 7:02 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240605064945.369310-6-mattias.ronnblom@ericsson.com>
2024-06-05 6:34 ` qemudev [this message]
2024-06-05 6:38 ` qemudev
2024-06-05 7:01 ` |SUCCESS| pw140739 " checkpatch
2024-06-05 8:04 ` |FAILURE| " 0-day Robot
2024-06-05 9:03 ` |SUCCESS| pw140738-140739 [PATCH] [5/5] eal: provide option to use c dpdklab
2024-06-05 9:03 ` dpdklab
2024-06-05 9:07 ` dpdklab
2024-06-05 9:08 ` dpdklab
2024-06-05 9:28 ` dpdklab
2024-06-05 9:28 ` dpdklab
2024-06-05 9:28 ` dpdklab
2024-06-05 9:28 ` dpdklab
2024-06-05 9:28 ` dpdklab
2024-06-05 9:29 ` dpdklab
2024-06-05 9:29 ` dpdklab
2024-06-05 9:30 ` dpdklab
2024-06-05 9:30 ` dpdklab
2024-06-05 9:31 ` dpdklab
2024-06-05 9:31 ` dpdklab
2024-06-05 9:31 ` dpdklab
2024-06-05 9:31 ` dpdklab
2024-06-05 9:31 ` dpdklab
2024-06-05 9:32 ` dpdklab
2024-06-05 9:32 ` dpdklab
2024-06-05 9:33 ` dpdklab
2024-06-05 9:33 ` dpdklab
2024-06-05 9:33 ` dpdklab
2024-06-05 9:33 ` dpdklab
2024-06-05 9:34 ` dpdklab
2024-06-05 9:34 ` dpdklab
2024-06-05 9:34 ` dpdklab
2024-06-05 9:37 ` dpdklab
2024-06-05 9:45 ` dpdklab
2024-06-05 9:46 ` dpdklab
2024-06-05 9:47 ` dpdklab
2024-06-05 9:47 ` dpdklab
2024-06-05 9:50 ` dpdklab
2024-06-05 9:52 ` dpdklab
2024-06-05 10:02 ` dpdklab
2024-06-05 10:06 ` dpdklab
2024-06-05 10:06 ` dpdklab
2024-06-05 10:07 ` |FAILURE| " dpdklab
2024-06-05 10:07 ` |SUCCESS| " dpdklab
2024-06-05 10:07 ` dpdklab
2024-06-05 10:09 ` dpdklab
2024-06-05 10:10 ` dpdklab
2024-06-05 10:17 ` dpdklab
2024-06-05 10:18 ` dpdklab
2024-06-05 10:19 ` dpdklab
2024-06-05 10:20 ` dpdklab
2024-06-05 10:20 ` dpdklab
2024-06-05 10:22 ` dpdklab
2024-06-05 10:31 ` dpdklab
2024-06-05 10:31 ` |WARNING| " dpdklab
2024-06-05 10:31 ` |FAILURE| " dpdklab
2024-06-05 10:34 ` dpdklab
2024-06-05 10:34 ` |SUCCESS| " dpdklab
2024-06-05 10:35 ` |FAILURE| " dpdklab
2024-06-05 10:42 ` |SUCCESS| " dpdklab
2024-06-05 10:42 ` |WARNING| " dpdklab
2024-06-05 10:45 ` |FAILURE| " dpdklab
2024-06-05 10:46 ` |WARNING| " dpdklab
2024-06-05 10:47 ` |FAILURE| " dpdklab
2024-06-05 10:48 ` |SUCCESS| " dpdklab
2024-06-05 10:55 ` dpdklab
2024-06-05 11:13 ` |WARNING| " dpdklab
2024-06-05 11:15 ` |SUCCESS| " dpdklab
2024-06-05 11:17 ` |FAILURE| " dpdklab
2024-06-05 11:18 ` dpdklab
2024-06-05 11:19 ` |SUCCESS| " dpdklab
2024-06-05 11:19 ` dpdklab
2024-06-05 11:19 ` |FAILURE| " dpdklab
2024-06-05 11:20 ` |SUCCESS| " dpdklab
2024-06-05 11:20 ` |FAILURE| " dpdklab
2024-06-05 11:30 ` dpdklab
2024-06-05 11:31 ` |SUCCESS| " dpdklab
2024-06-05 11:31 ` dpdklab
2024-06-05 11:33 ` |FAILURE| " dpdklab
2024-06-05 11:37 ` |SUCCESS| " dpdklab
2024-06-05 11:38 ` dpdklab
2024-06-05 11:51 ` dpdklab
2024-06-05 12:17 ` dpdklab
2024-06-05 12:35 ` dpdklab
2024-06-05 12:41 ` dpdklab
2024-06-05 13:02 ` dpdklab
2024-06-05 13:07 ` dpdklab
2024-06-05 13:58 ` dpdklab
2024-06-05 20:48 ` dpdklab
2024-06-05 21:54 ` dpdklab
2024-06-05 21:58 ` dpdklab
2024-06-05 22:16 ` 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=202406050634.4556Y98r3654443@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).