From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140237 [PATCH v2] hash: provide crc32 functions based on intrinsics
Date: Wed, 22 May 2024 07:36:20 +0800 [thread overview]
Message-ID: <202405212336.44LNaKbv838623@localhost.localdomain> (raw)
In-Reply-To: <1716336134-27366-2-git-send-email-roretzla@linux.microsoft.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140237
_Compilation OK_
Submitter: Tyler Retzlaff <roretzla@linux.microsoft.com>
Date: Tue, 21 May 2024 17:02:14 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6f80df8cb0f889203d7cd27766abcc6ebc720e33
140237 --> 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-05-22 0:04 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1716336134-27366-2-git-send-email-roretzla@linux.microsoft.com>
2024-05-21 23:36 ` qemudev [this message]
2024-05-21 23:40 ` qemudev
2024-05-22 0:03 ` checkpatch
2024-05-22 1:04 ` 0-day Robot
2024-05-22 1:12 ` |SUCCESS| pw140237 [PATCH] [v2] hash: provide crc32 functions based dpdklab
2024-05-22 1:12 ` dpdklab
2024-05-22 1:13 ` dpdklab
2024-05-22 1:13 ` dpdklab
2024-05-22 1:14 ` dpdklab
2024-05-22 1:14 ` dpdklab
2024-05-22 1:14 ` dpdklab
2024-05-22 1:15 ` dpdklab
2024-05-22 1:15 ` dpdklab
2024-05-22 1:15 ` dpdklab
2024-05-22 1:16 ` dpdklab
2024-05-22 1:18 ` dpdklab
2024-05-22 1:18 ` dpdklab
2024-05-22 1:18 ` dpdklab
2024-05-22 1:19 ` dpdklab
2024-05-22 1:19 ` dpdklab
2024-05-22 1:19 ` dpdklab
2024-05-22 1:19 ` dpdklab
2024-05-22 1:20 ` dpdklab
2024-05-22 1:20 ` dpdklab
2024-05-22 1:20 ` dpdklab
2024-05-22 1:20 ` dpdklab
2024-05-22 1:20 ` dpdklab
2024-05-22 1:21 ` dpdklab
2024-05-22 1:21 ` dpdklab
2024-05-22 1:21 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:22 ` dpdklab
2024-05-22 1:23 ` dpdklab
2024-05-22 1:23 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:24 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:25 ` dpdklab
2024-05-22 1:26 ` dpdklab
2024-05-22 1:26 ` dpdklab
2024-05-22 1:26 ` dpdklab
2024-05-22 1:26 ` dpdklab
2024-05-22 1:26 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:27 ` dpdklab
2024-05-22 1:28 ` dpdklab
2024-05-22 1:29 ` dpdklab
2024-05-22 1:31 ` dpdklab
2024-05-22 1:32 ` dpdklab
2024-05-22 1:33 ` dpdklab
2024-05-22 1:33 ` dpdklab
2024-05-22 1:34 ` dpdklab
2024-05-22 1:35 ` dpdklab
2024-05-22 1:36 ` dpdklab
2024-05-22 1:36 ` dpdklab
2024-05-22 1:39 ` dpdklab
2024-05-22 1:39 ` dpdklab
2024-05-22 1:40 ` dpdklab
2024-05-22 1:43 ` dpdklab
2024-05-22 1:43 ` dpdklab
2024-05-22 1:44 ` dpdklab
2024-05-22 1:46 ` dpdklab
2024-05-22 1:50 ` dpdklab
2024-05-22 1:50 ` dpdklab
2024-05-22 1:54 ` dpdklab
2024-05-22 2:07 ` dpdklab
2024-05-22 2:10 ` dpdklab
2024-05-22 2:13 ` dpdklab
2024-05-22 2:27 ` dpdklab
2024-05-22 2:43 ` dpdklab
2024-05-22 3:51 ` dpdklab
2024-05-23 6:07 ` 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=202405212336.44LNaKbv838623@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).