automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw152427-152438 [PATCH v4 14/14] net/zxdh: fix debugging errors
Date: Mon, 17 Mar 2025 22:43:46 +0800	[thread overview]
Message-ID: <202503171443.52HEhk2Z2526807@localhost.localdomain> (raw)
In-Reply-To: <20250317145802.1819809-15-chen.bingbin@zte.com.cn>

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

_Compilation OK_

Submitter: Bingbin Chen <chen.bingbin@zte.com.cn>
Date: Mon, 17 Mar 2025 22:57:49 +0800
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 9694dcd7d1abe20a6a838b80a6309137e02c3789

152427-152438 --> 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-03-17 15:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250317145802.1819809-15-chen.bingbin@zte.com.cn>
2025-03-17 14:43 ` qemudev [this message]
2025-03-17 14:48 ` qemudev
2025-03-17 15:18 ` |SUCCESS| pw152438 " checkpatch
2025-03-17 16:03 ` 0-day Robot
2025-03-17 16:28 ` |SUCCESS| pw152427-152438 [PATCH] [v4,14/14] net/zxdh: fix debugging dpdklab
2025-03-17 16:32 ` |PENDING| " dpdklab
2025-03-17 16:34 ` |SUCCESS| " dpdklab
2025-03-17 16:37 ` dpdklab
2025-03-17 16:38 ` dpdklab
2025-03-17 16:40 ` |PENDING| " dpdklab
2025-03-17 16:43 ` |SUCCESS| " dpdklab
2025-03-17 16:49 ` dpdklab
2025-03-17 16:56 ` dpdklab
2025-03-17 17:01 ` dpdklab
2025-03-17 17:03 ` dpdklab
2025-03-17 17:04 ` |PENDING| " dpdklab
2025-03-17 17:07 ` |SUCCESS| " dpdklab
2025-03-17 17:09 ` dpdklab
2025-03-17 17:34 ` dpdklab
2025-03-17 17:41 ` dpdklab
2025-03-17 17:48 ` dpdklab
2025-03-17 18:39 ` 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=202503171443.52HEhk2Z2526807@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).