automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138009 [PATCH v3] lib/hash: add defer queue reclaim API
Date: Wed, 6 Mar 2024 16:40:02 +0800	[thread overview]
Message-ID: <202403060840.4268e2GO2710466@localhost.localdomain> (raw)
In-Reply-To: <20240306085948.185299-1-aomeryamac@gmail.com>

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

_Compilation OK_

Submitter: Abdullah Ömer Yamaç <aomeryamac@gmail.com>
Date: Wed,  6 Mar 2024 08:59:48 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7fcf4e8a03c4b0d2c6cec11ddd18c7bf88ba0384

138009 --> 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-03-06  9:04 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240306085948.185299-1-aomeryamac@gmail.com>
2024-03-06  8:40 ` qemudev [this message]
2024-03-06  8:44 ` qemudev
2024-03-06  9:01 ` checkpatch
2024-03-06 10:04 ` |FAILURE| " 0-day Robot
2024-03-06 10:57 ` |SUCCESS| pw138009 [PATCH] [v3] lib/hash: add defer queue reclaim AP dpdklab
2024-03-06 10:57 ` dpdklab
2024-03-06 10:57 ` dpdklab
2024-03-06 10:58 ` dpdklab
2024-03-06 10:58 ` dpdklab
2024-03-06 11:05 ` dpdklab
2024-03-06 11:05 ` dpdklab
2024-03-06 11:06 ` dpdklab
2024-03-06 11:06 ` dpdklab
2024-03-06 11:07 ` dpdklab
2024-03-06 11:25 ` dpdklab
2024-03-06 11:25 ` dpdklab
2024-03-06 12:03 ` dpdklab
2024-03-06 12:03 ` dpdklab
2024-03-06 12:03 ` dpdklab
2024-03-06 12:04 ` dpdklab
2024-03-06 12:06 ` dpdklab
2024-03-06 12:07 ` dpdklab
2024-03-06 12:08 ` dpdklab
2024-03-06 12:09 ` dpdklab
2024-03-06 12:09 ` dpdklab
2024-03-06 12:14 ` dpdklab
2024-03-06 13:08 ` dpdklab
2024-03-06 13:10 ` dpdklab
2024-03-06 13:17 ` dpdklab
2024-03-06 13:19 ` dpdklab
2024-03-06 13:20 ` dpdklab
2024-03-06 13:20 ` dpdklab
2024-03-06 13:21 ` dpdklab
2024-03-06 13:25 ` dpdklab
2024-03-06 13:26 ` dpdklab
2024-03-06 13:29 ` dpdklab
2024-03-06 13:31 ` dpdklab
2024-03-06 13:31 ` dpdklab
2024-03-06 13:32 ` dpdklab
2024-03-06 13:33 ` dpdklab
2024-03-06 13:33 ` dpdklab
2024-03-06 13:35 ` dpdklab
2024-03-06 13:35 ` dpdklab
2024-03-06 13:36 ` dpdklab
2024-03-06 13:36 ` dpdklab
2024-03-06 13:37 ` dpdklab
2024-03-06 13:37 ` dpdklab
2024-03-06 13:37 ` dpdklab
2024-03-06 13:38 ` dpdklab
2024-03-06 13:38 ` dpdklab
2024-03-06 13:45 ` dpdklab
2024-03-06 13:46 ` dpdklab
2024-03-06 13:46 ` dpdklab
2024-03-06 13:47 ` dpdklab
2024-03-06 13:47 ` dpdklab
2024-03-06 13:47 ` dpdklab
2024-03-06 13:53 ` dpdklab
2024-03-06 13:54 ` dpdklab
2024-03-06 13:54 ` dpdklab
2024-03-06 13:54 ` dpdklab
2024-03-06 13:55 ` dpdklab
2024-03-06 13:56 ` dpdklab
2024-03-06 13:59 ` dpdklab
2024-03-06 14:03 ` dpdklab
2024-03-06 14:04 ` dpdklab
2024-03-06 14:13 ` dpdklab
2024-03-06 14:26 ` dpdklab
2024-03-06 14:48 ` dpdklab
2024-03-06 14:50 ` dpdklab
2024-03-06 14:53 ` dpdklab
2024-03-06 15:46 ` dpdklab
2024-03-06 15:54 ` dpdklab
2024-03-06 16:13 ` dpdklab
2024-03-06 16:19 ` dpdklab
2024-03-06 18:00 ` dpdklab
2024-03-11  3:14 ` 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=202403060840.4268e2GO2710466@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).