From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142156-142162 [PATCH v11 7/7] hash: add SVE support for bulk key lookup
Date: Sat, 6 Jul 2024 01:23:15 +0800 [thread overview]
Message-ID: <202407051723.465HNFB21556561@localhost.localdomain> (raw)
In-Reply-To: <20240705174526.3035295-8-yoan.picchi@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/142162
_Compilation OK_
Submitter: Yoan Picchi <yoan.picchi@arm.com>
Date: Fri, 5 Jul 2024 17:45:20 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: fcfb19cda4f6439f260cdeabb6c44d3c6f0d5fc4
142156-142162 --> 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-07-05 17:52 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240705174526.3035295-8-yoan.picchi@arm.com>
2024-07-05 17:23 ` qemudev [this message]
2024-07-05 17:28 ` qemudev
2024-07-05 17:46 ` |SUCCESS| pw142162 " checkpatch
2024-07-05 18:43 ` 0-day Robot
2024-07-07 11:03 ` |SUCCESS| pw142156-142162 [PATCH] [v11,7/7] hash: add SVE support fo dpdklab
2024-07-07 11:08 ` dpdklab
2024-07-07 11:12 ` dpdklab
2024-07-07 11:14 ` |PENDING| " dpdklab
2024-07-07 11:17 ` dpdklab
2024-07-07 11:18 ` dpdklab
2024-07-07 11:18 ` dpdklab
2024-07-07 11:19 ` dpdklab
2024-07-07 11:20 ` dpdklab
2024-07-07 11:21 ` |SUCCESS| " dpdklab
2024-07-07 11:23 ` |PENDING| " dpdklab
2024-07-07 11:25 ` |SUCCESS| " dpdklab
2024-07-07 11:25 ` dpdklab
2024-07-07 11:25 ` dpdklab
2024-07-07 11:29 ` dpdklab
2024-07-07 11:37 ` |PENDING| " dpdklab
2024-07-07 11:38 ` dpdklab
2024-07-07 11:44 ` dpdklab
2024-07-07 11:48 ` dpdklab
2024-07-07 11:49 ` |SUCCESS| " dpdklab
2024-07-07 11:53 ` dpdklab
2024-07-07 11:57 ` dpdklab
2024-07-07 11:58 ` |PENDING| " dpdklab
2024-07-07 12:00 ` dpdklab
2024-07-07 12:03 ` dpdklab
2024-07-07 12:07 ` dpdklab
2024-07-07 12:07 ` dpdklab
2024-07-07 12:07 ` dpdklab
2024-07-07 12:09 ` dpdklab
2024-07-07 12:10 ` dpdklab
2024-07-07 12:17 ` dpdklab
2024-07-07 12:17 ` |SUCCESS| " dpdklab
2024-07-07 12:21 ` dpdklab
2024-07-07 12:24 ` |PENDING| " dpdklab
2024-07-07 12:25 ` dpdklab
2024-07-07 12:26 ` dpdklab
2024-07-07 12:27 ` dpdklab
2024-07-07 12:28 ` dpdklab
2024-07-07 12:28 ` dpdklab
2024-07-07 12:31 ` dpdklab
2024-07-07 12:35 ` dpdklab
2024-07-07 12:35 ` dpdklab
2024-07-07 12:36 ` dpdklab
2024-07-07 12:37 ` dpdklab
2024-07-07 12:38 ` dpdklab
2024-07-07 12:39 ` dpdklab
2024-07-07 12:40 ` dpdklab
2024-07-07 12:40 ` dpdklab
2024-07-07 12:42 ` dpdklab
2024-07-07 12:43 ` dpdklab
2024-07-07 12:45 ` |SUCCESS| " dpdklab
2024-07-07 12:48 ` |PENDING| " dpdklab
2024-07-07 12:49 ` dpdklab
2024-07-07 12:53 ` dpdklab
2024-07-07 12:55 ` dpdklab
2024-07-07 12:56 ` dpdklab
2024-07-07 13:01 ` dpdklab
2024-07-07 13:02 ` dpdklab
2024-07-07 13:02 ` dpdklab
2024-07-07 13:02 ` dpdklab
2024-07-07 13:02 ` dpdklab
2024-07-07 13:03 ` dpdklab
2024-07-07 13:07 ` dpdklab
2024-07-07 13:08 ` dpdklab
2024-07-07 13:09 ` dpdklab
2024-07-07 13:10 ` dpdklab
2024-07-07 13:12 ` dpdklab
2024-07-07 13:12 ` dpdklab
2024-07-07 13:13 ` dpdklab
2024-07-07 13:13 ` dpdklab
2024-07-07 13:14 ` dpdklab
2024-07-07 13:16 ` dpdklab
2024-07-07 13:16 ` dpdklab
2024-07-07 13:17 ` |SUCCESS| " dpdklab
2024-07-07 13:25 ` |PENDING| " dpdklab
2024-07-07 13:28 ` dpdklab
2024-07-07 13:31 ` dpdklab
2024-07-07 13:31 ` |SUCCESS| " dpdklab
2024-07-07 13:32 ` dpdklab
2024-07-07 13:43 ` |PENDING| " dpdklab
2024-07-09 9:58 ` |SUCCESS| " dpdklab
2024-07-09 10:11 ` dpdklab
2024-07-14 0:25 ` dpdklab
2024-07-14 11:11 ` dpdklab
2024-07-14 17:42 ` dpdklab
2024-07-15 11:58 ` dpdklab
2024-07-15 12:17 ` 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=202407051723.465HNFB21556561@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).