From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation size
Date: Wed, 17 Apr 2024 21:19:08 +0800 [thread overview]
Message-ID: <202404171319.43HDJ8r83488113@localhost.localdomain> (raw)
In-Reply-To: <20240417133929.711268-1-aomeryamac@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139450
_Compilation OK_
Submitter: Abdullah Ömer Yamaç <aomeryamac@gmail.com>
Date: Wed, 17 Apr 2024 13:39:29 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c
139450 --> 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 13:44 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240417133929.711268-1-aomeryamac@gmail.com>
2024-04-17 13:19 ` qemudev [this message]
2024-04-17 13:23 ` qemudev
2024-04-17 13:40 ` checkpatch
2024-04-17 14:28 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation dpdklab
2024-04-17 14:29 ` dpdklab
2024-04-17 14:30 ` dpdklab
2024-04-17 14:30 ` dpdklab
2024-04-17 14:31 ` dpdklab
2024-04-17 14:32 ` dpdklab
2024-04-17 14:40 ` dpdklab
2024-04-17 14:40 ` dpdklab
2024-04-17 14:41 ` dpdklab
2024-04-17 14:41 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:42 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:43 ` dpdklab
2024-04-17 14:44 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation size 0-day Robot
2024-04-17 14:46 ` |SUCCESS| pw139450 [PATCH] lib/hash: setting the maximum reclamation dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:46 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:47 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:48 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:49 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:51 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:52 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:53 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:54 ` dpdklab
2024-04-17 14:55 ` dpdklab
2024-04-17 14:55 ` dpdklab
2024-04-17 14:58 ` dpdklab
2024-04-17 14:58 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 14:59 ` dpdklab
2024-04-17 15:01 ` dpdklab
2024-04-17 15:01 ` dpdklab
2024-04-17 15:02 ` dpdklab
2024-04-17 15:08 ` dpdklab
2024-04-17 15:35 ` dpdklab
2024-04-17 15:36 ` dpdklab
2024-04-17 15:37 ` dpdklab
2024-04-17 15:38 ` dpdklab
2024-04-17 15:40 ` dpdklab
2024-04-17 16:14 ` dpdklab
2024-04-17 16:19 ` dpdklab
2024-04-17 16:42 ` 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=202404171319.43HDJ8r83488113@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).