From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw129126 [PATCH v8] hash: add XOR32 hash function
Date: Fri, 30 Jun 2023 01:21:14 +0800 [thread overview]
Message-ID: <202306291721.35THLEke601317@localhost.localdomain> (raw)
In-Reply-To: <20230629173304.2195376-1-qobilidop@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/129126
_Compilation OK_
Submitter: Bili Dong <qobilidop@gmail.com>
Date: Thu, 29 Jun 2023 17:33:00 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 93a4b3beba4ee611685148917981f846427cafb2
129126 --> 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:[~2023-06-29 17:35 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230629173304.2195376-1-qobilidop@gmail.com>
2023-06-29 17:21 ` qemudev [this message]
2023-06-29 17:25 ` qemudev
2023-06-29 17:35 ` checkpatch
2023-06-29 19:03 |SUCCESS| pw129126 [PATCH] [v8] " dpdklab
2023-06-29 19:03 dpdklab
2023-06-29 19:10 dpdklab
2023-06-29 19:10 dpdklab
2023-06-29 19:12 dpdklab
2023-06-29 19:16 dpdklab
2023-06-29 19:35 dpdklab
2023-06-29 19:38 dpdklab
2023-06-29 19:39 dpdklab
2023-06-29 19:39 dpdklab
2023-06-29 19:40 dpdklab
2023-06-29 19:51 dpdklab
2023-06-29 19:51 dpdklab
2023-06-29 20:00 dpdklab
2023-06-29 20:00 dpdklab
2023-06-29 20:07 dpdklab
2023-06-29 21:04 dpdklab
2023-06-29 21:14 dpdklab
2023-06-29 21:25 dpdklab
2023-06-29 21:52 dpdklab
2023-06-29 22:06 dpdklab
2023-06-30 0:27 dpdklab
2023-06-30 0:28 dpdklab
2023-06-30 12:30 dpdklab
2023-06-30 12:46 dpdklab
2023-06-30 12:51 dpdklab
2023-06-30 12:56 dpdklab
2023-06-30 13:06 dpdklab
2023-07-01 19:39 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=202306291721.35THLEke601317@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).