automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140125 [PATCH v6] lib/hash: add defer queue reclaim API
Date: Wed, 15 May 2024 18:30:34 +0800	[thread overview]
Message-ID: <202405151030.44FAUY043871347@localhost.localdomain> (raw)
In-Reply-To: <20240515105446.1251717-1-aomeryamac@gmail.com>

Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140125

_Compilation OK_

Submitter: Abdullah Ömer Yamaç <aomeryamac@gmail.com>
Date: Wed, 15 May 2024 10:54:46 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

140125 --> 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


       reply	other threads:[~2024-05-15 10:58 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240515105446.1251717-1-aomeryamac@gmail.com>
2024-05-15 10:30 ` qemudev [this message]
2024-05-15 10:34 ` qemudev
2024-05-15 10:55 ` checkpatch
2024-05-15 11:44 ` 0-day Robot
2024-05-15 18:29 ` |SUCCESS| pw140125 [PATCH] [v6] lib/hash: add defer queue reclaim AP dpdklab
2024-05-15 18:30 ` dpdklab
2024-05-15 18:30 ` dpdklab
2024-05-15 18:32 ` dpdklab
2024-05-15 18:33 ` dpdklab
2024-05-15 18:57 ` dpdklab
2024-05-15 19:01 ` dpdklab
2024-05-15 19:02 ` dpdklab
2024-05-15 19:03 ` dpdklab
2024-05-15 19:03 ` dpdklab
2024-05-15 19:03 ` dpdklab
2024-05-15 19:04 ` dpdklab
2024-05-15 19:05 ` dpdklab
2024-05-15 19:05 ` dpdklab
2024-05-15 19:05 ` dpdklab
2024-05-15 19:06 ` dpdklab
2024-05-15 19:06 ` dpdklab
2024-05-15 19:06 ` dpdklab
2024-05-15 19:06 ` dpdklab
2024-05-15 19:07 ` dpdklab
2024-05-15 19:07 ` dpdklab
2024-05-15 19:07 ` dpdklab
2024-05-15 19:08 ` dpdklab
2024-05-15 19:08 ` dpdklab
2024-05-15 19:08 ` dpdklab
2024-05-15 19:09 ` dpdklab
2024-05-15 19:09 ` dpdklab
2024-05-15 19:09 ` dpdklab
2024-05-15 19:10 ` dpdklab
2024-05-15 19:10 ` dpdklab
2024-05-15 19:10 ` dpdklab
2024-05-15 19:11 ` dpdklab
2024-05-15 19:11 ` dpdklab
2024-05-15 19:11 ` dpdklab
2024-05-15 19:12 ` dpdklab
2024-05-15 19:12 ` dpdklab
2024-05-15 19:13 ` dpdklab
2024-05-15 19:13 ` dpdklab
2024-05-15 19:13 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:14 ` dpdklab
2024-05-15 19:15 ` dpdklab
2024-05-15 19:15 ` dpdklab
2024-05-15 19:15 ` dpdklab
2024-05-15 19:15 ` dpdklab
2024-05-15 19:15 ` dpdklab
2024-05-15 19:16 ` dpdklab
2024-05-15 19:16 ` dpdklab
2024-05-15 19:16 ` dpdklab
2024-05-15 19:16 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:17 ` dpdklab
2024-05-15 19:18 ` dpdklab
2024-05-15 19:18 ` dpdklab
2024-05-15 19:19 ` dpdklab
2024-05-15 19:19 ` dpdklab
2024-05-15 19:19 ` dpdklab
2024-05-15 19:20 ` dpdklab
2024-05-15 19:21 ` dpdklab
2024-05-15 19:21 ` dpdklab
2024-05-15 19:24 ` dpdklab
2024-05-15 19:24 ` dpdklab
2024-05-15 19:24 ` dpdklab
2024-05-15 19:27 ` dpdklab
2024-05-15 19:29 ` dpdklab
2024-05-15 19:30 ` dpdklab
2024-05-15 19:31 ` dpdklab
2024-05-15 19:32 ` dpdklab
2024-05-15 19:36 ` dpdklab
2024-05-15 19:40 ` dpdklab
2024-05-15 19:44 ` dpdklab
2024-05-15 19:45 ` dpdklab
2024-05-15 19:49 ` dpdklab
2024-05-15 20:03 ` dpdklab
2024-05-15 20:12 ` dpdklab
2024-05-15 20:21 ` dpdklab
2024-05-15 20:48 ` dpdklab
2024-05-15 21:53 ` 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=202405151030.44FAUY043871347@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).