automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw151325 [PATCH v7] net: add thread-safe crc api
Date: Tue, 11 Feb 2025 16:29:15 +0800	[thread overview]
Message-ID: <202502110829.51B8TFYJ3683562@localhost.localdomain> (raw)
In-Reply-To: <20250211090202.1018656-1-arkadiuszx.kusztal@intel.com>

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

_Compilation OK_

Submitter: Arkadiusz Kusztal <arkadiuszx.kusztal@intel.com>
Date: Tue, 11 Feb 2025 09:02:02 +0000
DPDK git baseline: Repo:dpdk-next-crypto
  Branch: for-main
  CommitID: 7125636162d67b1c40ba6802a3ff4466d125d243

151325 --> 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:[~2025-02-11  9:05 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250211090202.1018656-1-arkadiuszx.kusztal@intel.com>
2025-02-11  8:29 ` qemudev [this message]
2025-02-11  8:33 ` qemudev
2025-02-11  9:02 ` |WARNING| " checkpatch
2025-02-11  9:57 ` |SUCCESS| pw151325 [PATCH] [v7] " dpdklab
2025-02-11 10:18 ` dpdklab
2025-02-11 10:25 ` |SUCCESS| pw151325 [PATCH v7] " 0-day Robot
2025-02-11 10:26 ` |SUCCESS| pw151325 [PATCH] [v7] " dpdklab
2025-02-11 10:26 ` dpdklab
2025-02-11 10:31 ` dpdklab
2025-02-11 10:33 ` dpdklab
2025-02-11 10:42 ` dpdklab
2025-02-11 10:44 ` dpdklab
2025-02-11 10:44 ` |PENDING| " dpdklab
2025-02-11 10:53 ` |SUCCESS| " dpdklab
2025-02-11 10:54 ` |PENDING| " dpdklab
2025-02-11 11:11 ` dpdklab
2025-02-11 12:20 ` dpdklab
2025-02-11 12:37 ` |SUCCESS| " dpdklab
2025-02-11 13:01 ` dpdklab
2025-02-11 13:46 ` dpdklab
2025-02-11 14:09 ` dpdklab
2025-02-11 14:30 ` 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=202502110829.51B8TFYJ3683562@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).