From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124334 [PATCH v6] hash: add XOR32 hash function
Date: Wed, 22 Feb 2023 03:32:03 +0800 [thread overview]
Message-ID: <202302211932.31LJW3Hq1419356@localhost.localdomain> (raw)
In-Reply-To: <20230221193710.717280-1-qobilidop@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124334
_Compilation OK_
Submitter: Bili Dong <qobilidop@gmail.com>
Date: Tue, 21 Feb 2023 19:37:10 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 9bd5ebca59c865aead7096358fb733e53a72007b
124334 --> 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-21 19:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221193710.717280-1-qobilidop@gmail.com>
2023-02-21 19:32 ` qemudev [this message]
2023-02-21 19:36 ` qemudev
2023-02-21 19:37 ` |WARNING| " checkpatch
2023-02-21 22:39 ` |SUCCESS| " 0-day Robot
2023-02-23 22:02 |SUCCESS| pw124334 [PATCH] [v6] " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-22 8:08 dpdklab
2023-02-22 6:25 dpdklab
2023-02-22 6:25 dpdklab
2023-02-22 6:22 dpdklab
2023-02-22 6:22 dpdklab
2023-02-22 6:20 dpdklab
2023-02-22 6:19 dpdklab
2023-02-22 6:18 dpdklab
2023-02-22 6:15 dpdklab
2023-02-22 5:56 dpdklab
2023-02-22 5:54 dpdklab
2023-02-22 5:50 dpdklab
2023-02-22 5:45 dpdklab
2023-02-22 5:37 dpdklab
2023-02-22 5:34 dpdklab
2023-02-21 23:01 dpdklab
2023-02-21 22:41 dpdklab
2023-02-21 21:52 dpdklab
2023-02-21 21:13 dpdklab
2023-02-21 21:06 dpdklab
2023-02-21 20:55 dpdklab
2023-02-21 20:51 dpdklab
2023-02-21 20:13 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=202302211932.31LJW3Hq1419356@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).