From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139452-139454 [PATCH v8 4/4] hash: add SVE support for bulk key lookup
Date: Wed, 17 Apr 2024 23:46:57 +0800 [thread overview]
Message-ID: <202404171546.43HFkvR91104847@localhost.localdomain> (raw)
In-Reply-To: <20240417160807.1249480-5-yoan.picchi@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139454
_Compilation OK_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Wed, 17 Apr 2024 16:08:04 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139452-139454 --> 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-04-17 16:11 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417160807.1249480-5-yoan.picchi@arm.com>
2024-04-17 15:46 ` qemudev [this message]
2024-04-17 15:51 ` qemudev
2024-04-17 16:10 ` |SUCCESS| pw139454 " checkpatch
2024-04-17 17:05 ` 0-day Robot
2024-04-17 17:32 ` |SUCCESS| pw139452-139454 [PATCH] [v8,4/4] hash: add SVE support for dpdklab
2024-04-17 17:34 ` dpdklab
2024-04-17 17:35 ` dpdklab
2024-04-17 17:36 ` dpdklab
2024-04-17 17:36 ` dpdklab
2024-04-17 17:40 ` dpdklab
2024-04-17 17:41 ` dpdklab
2024-04-17 17:59 ` dpdklab
2024-04-17 17:59 ` dpdklab
2024-04-17 18:00 ` dpdklab
2024-04-17 18:02 ` dpdklab
2024-04-17 18:03 ` dpdklab
2024-04-17 18:03 ` dpdklab
2024-04-17 18:04 ` dpdklab
2024-04-17 18:04 ` dpdklab
2024-04-17 18:06 ` dpdklab
2024-04-17 18:07 ` dpdklab
2024-04-17 18:07 ` dpdklab
2024-04-17 18:08 ` dpdklab
2024-04-17 18:08 ` dpdklab
2024-04-17 18:09 ` dpdklab
2024-04-17 18:09 ` dpdklab
2024-04-17 18:10 ` dpdklab
2024-04-17 18:12 ` dpdklab
2024-04-17 18:12 ` dpdklab
2024-04-17 18:13 ` dpdklab
2024-04-17 18:13 ` dpdklab
2024-04-17 18:14 ` dpdklab
2024-04-17 18:14 ` dpdklab
2024-04-17 18:15 ` dpdklab
2024-04-17 18:15 ` dpdklab
2024-04-17 18:16 ` dpdklab
2024-04-17 18:16 ` dpdklab
2024-04-17 18:16 ` dpdklab
2024-04-17 18:17 ` dpdklab
2024-04-17 18:17 ` dpdklab
2024-04-17 18:17 ` dpdklab
2024-04-17 18:18 ` dpdklab
2024-04-17 18:19 ` dpdklab
2024-04-17 18:19 ` dpdklab
2024-04-17 18:20 ` dpdklab
2024-04-17 18:20 ` dpdklab
2024-04-17 18:21 ` dpdklab
2024-04-17 18:21 ` dpdklab
2024-04-17 18:21 ` dpdklab
2024-04-17 18:22 ` dpdklab
2024-04-17 18:22 ` dpdklab
2024-04-17 18:22 ` dpdklab
2024-04-17 18:23 ` dpdklab
2024-04-17 18:23 ` dpdklab
2024-04-17 18:24 ` dpdklab
2024-04-17 18:24 ` dpdklab
2024-04-17 18:24 ` dpdklab
2024-04-17 18:24 ` dpdklab
2024-04-17 18:25 ` dpdklab
2024-04-17 18:26 ` dpdklab
2024-04-17 18:26 ` dpdklab
2024-04-17 18:27 ` dpdklab
2024-04-17 18:27 ` dpdklab
2024-04-17 18:27 ` dpdklab
2024-04-17 18:28 ` dpdklab
2024-04-17 18:28 ` dpdklab
2024-04-17 18:29 ` dpdklab
2024-04-17 18:30 ` dpdklab
2024-04-17 18:32 ` dpdklab
2024-04-17 18:32 ` dpdklab
2024-04-17 18:33 ` dpdklab
2024-04-17 18:34 ` dpdklab
2024-04-17 18:34 ` dpdklab
2024-04-17 18:35 ` dpdklab
2024-04-17 18:35 ` dpdklab
2024-04-17 18:36 ` dpdklab
2024-04-17 18:38 ` dpdklab
2024-04-17 18:38 ` dpdklab
2024-04-17 18:39 ` dpdklab
2024-04-17 18:39 ` dpdklab
2024-04-17 18:40 ` dpdklab
2024-04-17 18:53 ` dpdklab
2024-04-17 18:53 ` dpdklab
2024-04-17 18:59 ` dpdklab
2024-04-17 19:03 ` dpdklab
2024-04-17 19:08 ` dpdklab
2024-04-17 19:23 ` dpdklab
2024-04-17 19:26 ` dpdklab
2024-04-17 19:26 ` dpdklab
2024-04-17 19:27 ` dpdklab
2024-04-17 19:31 ` dpdklab
2024-04-17 20:27 ` dpdklab
2024-04-17 21:03 ` 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=202404171546.43HFkvR91104847@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).