From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw145844 [PATCH v3] hash: separate param checks in hash create func
Date: Mon, 14 Oct 2024 18:19:07 +0800 [thread overview]
Message-ID: <202410141019.49EAJ7BR2169175@localhost.localdomain> (raw)
In-Reply-To: <20241014101916.2043948-1-niall.meade@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/145844
_Compilation OK_
Submitter: Niall Meade <niall.meade@intel.com>
Date: Mon, 14 Oct 2024 10:19:16 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3423756cf2e33cb222c2f82361c11f5d83a48ba3
145844 --> 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-10-14 10:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241014101916.2043948-1-niall.meade@intel.com>
2024-10-14 10:19 ` qemudev [this message]
2024-10-14 10:21 ` checkpatch
2024-10-14 10:23 ` qemudev
2024-10-14 12:02 ` 0-day Robot
2024-10-15 0:26 ` |SUCCESS| pw145844 [PATCH] [v3] hash: separate param checks in hash dpdklab
2024-10-15 0:51 ` dpdklab
2024-10-15 1:28 ` dpdklab
2024-10-15 2:43 ` dpdklab
2024-10-15 7:43 ` |FAILURE| " dpdklab
2024-10-15 9:23 ` dpdklab
2024-10-15 9:31 ` dpdklab
2024-10-15 11:15 ` |WARNING| " dpdklab
2024-10-16 18:58 ` |SUCCESS| " dpdklab
2024-10-16 20:28 ` dpdklab
2024-10-17 11:29 ` |FAILURE| " dpdklab
2024-10-17 23:45 ` dpdklab
2024-10-20 3:11 ` |SUCCESS| " dpdklab
2024-10-20 19:07 ` |PENDING| " dpdklab
2024-10-20 20:42 ` |WARNING| " dpdklab
2024-10-20 22:13 ` |FAILURE| " dpdklab
2024-10-20 22:23 ` |WARNING| " dpdklab
2024-10-20 22:27 ` dpdklab
2024-10-20 22:33 ` dpdklab
2024-10-20 22:35 ` dpdklab
2024-10-20 22:36 ` dpdklab
2024-10-20 22:39 ` dpdklab
2024-10-20 22:45 ` dpdklab
2024-10-20 22:52 ` dpdklab
2024-10-20 23:07 ` dpdklab
2024-10-20 23:08 ` dpdklab
2024-10-20 23:29 ` dpdklab
2024-10-20 23:38 ` dpdklab
2024-10-20 23:41 ` dpdklab
2024-10-20 23:44 ` dpdklab
2024-10-20 23:46 ` dpdklab
2024-10-21 3:00 ` |FAILURE| " dpdklab
2024-10-21 3:32 ` dpdklab
2024-10-21 5:12 ` dpdklab
2024-10-22 8:51 ` dpdklab
2024-10-22 11:04 ` |SUCCESS| " dpdklab
2024-10-22 11:06 ` dpdklab
2024-10-22 11:07 ` dpdklab
2024-10-23 4:02 ` |WARNING| " dpdklab
2024-10-23 4:35 ` 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=202410141019.49EAJ7BR2169175@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).