From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138645-138644 [PATCH 2/2] eal: add rte ffs32 and rte ffs64 inline functions
Date: Thu, 21 Mar 2024 05:23:49 +0800 [thread overview]
Message-ID: <202403202123.42KLNnaU328188@localhost.localdomain> (raw)
In-Reply-To: <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138644
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Wed, 20 Mar 2024 14:24:38 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138645-138644 --> 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-03-20 21:51 UTC|newest]
Thread overview: 83+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1710969879-23701-3-git-send-email-roretzla@linux.microsoft.com>
2024-03-20 21:23 ` qemudev [this message]
2024-03-20 21:26 ` |WARNING| pw138644 " checkpatch
2024-03-20 21:27 ` |SUCCESS| pw138645-138644 " qemudev
2024-03-20 22:24 ` |SUCCESS| pw138644 " 0-day Robot
2024-03-21 2:18 ` |SUCCESS| pw138645-138644 [PATCH] [2/2] eal: add rte ffs32 and rte f dpdklab
2024-03-21 2:18 ` dpdklab
2024-03-21 2:19 ` dpdklab
2024-03-21 2:20 ` dpdklab
2024-03-21 2:20 ` dpdklab
2024-03-21 2:21 ` dpdklab
2024-03-21 2:21 ` dpdklab
2024-03-21 2:23 ` dpdklab
2024-03-21 2:24 ` dpdklab
2024-03-21 2:25 ` dpdklab
2024-03-21 2:26 ` dpdklab
2024-03-21 2:29 ` dpdklab
2024-03-21 2:31 ` dpdklab
2024-03-21 2:35 ` dpdklab
2024-03-21 2:39 ` dpdklab
2024-03-21 2:57 ` dpdklab
2024-03-21 3:06 ` dpdklab
2024-03-21 3:07 ` dpdklab
2024-03-21 3:08 ` dpdklab
2024-03-21 3:11 ` dpdklab
2024-03-21 3:11 ` dpdklab
2024-03-21 3:19 ` dpdklab
2024-03-21 3:32 ` dpdklab
2024-03-21 3:44 ` dpdklab
2024-03-21 3:44 ` dpdklab
2024-03-21 3:46 ` dpdklab
2024-03-21 3:46 ` dpdklab
2024-03-21 3:47 ` dpdklab
2024-03-21 4:39 ` dpdklab
2024-03-21 5:23 ` dpdklab
2024-03-21 5:41 ` dpdklab
2024-03-21 5:55 ` dpdklab
2024-03-21 5:55 ` dpdklab
2024-03-21 5:57 ` dpdklab
2024-03-21 5:58 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 5:59 ` dpdklab
2024-03-21 6:00 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:01 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:02 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:03 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:04 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:05 ` dpdklab
2024-03-21 6:07 ` dpdklab
2024-03-21 6:12 ` dpdklab
2024-03-21 6:12 ` dpdklab
2024-03-21 6:13 ` dpdklab
2024-03-21 6:13 ` dpdklab
2024-03-21 6:15 ` dpdklab
2024-03-21 6:16 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:17 ` dpdklab
2024-03-21 6:18 ` dpdklab
2024-03-21 6:20 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:30 ` dpdklab
2024-03-21 6:32 ` dpdklab
2024-03-21 6:34 ` dpdklab
2024-03-21 6:36 ` dpdklab
2024-03-21 7:55 ` dpdklab
2024-03-21 9:18 ` dpdklab
2024-03-21 10:58 ` dpdklab
2024-03-21 11:40 ` dpdklab
2024-03-21 18:09 ` dpdklab
2024-03-22 19:28 ` dpdklab
2024-03-22 20:23 ` 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=202403202123.42KLNnaU328188@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).