From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123945 [PATCH] hash: add XOR32 hash function
Date: Wed, 15 Feb 2023 18:27:06 +0800 [thread overview]
Message-ID: <202302151027.31FAR6Mg349376@localhost.localdomain> (raw)
In-Reply-To: <20230215103041.3861350-1-qobilidop@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123945
_Compilation OK_
Submitter: Bili Dong <qobilidop@gmail.com>
Date: Wed, 15 Feb 2023 10:30:41 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 04ed18cd41f12ea1487581731ef56185d902d827
123945 --> 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-02-15 10:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230215103041.3861350-1-qobilidop@gmail.com>
2023-02-15 10:27 ` qemudev [this message]
2023-02-15 10:31 ` qemudev
2023-02-15 10:33 ` |WARNING| " checkpatch
2023-02-15 10:58 |SUCCESS| " dpdklab
2023-02-15 11:01 dpdklab
2023-02-15 11:02 dpdklab
2023-02-15 11:02 dpdklab
2023-02-15 11:08 dpdklab
2023-02-15 11:10 dpdklab
2023-02-15 11:14 dpdklab
2023-02-15 11:15 dpdklab
2023-02-15 11:17 dpdklab
2023-02-15 11:22 dpdklab
2023-02-15 11:38 dpdklab
2023-02-15 11:43 dpdklab
2023-02-15 11:45 dpdklab
2023-02-15 11:51 dpdklab
2023-02-15 11:54 dpdklab
2023-02-15 12:02 dpdklab
2023-02-15 12:05 dpdklab
2023-02-15 12:07 dpdklab
2023-02-15 12:09 dpdklab
2023-02-15 12:11 dpdklab
2023-02-15 12:11 dpdklab
2023-02-15 12:13 dpdklab
2023-02-15 12:17 dpdklab
2023-02-15 12:17 dpdklab
2023-02-16 22:19 dpdklab
2023-02-18 19: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=202302151027.31FAR6Mg349376@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).