automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137877 [PATCH v4] net/ice: add diagnostic support in Tx path
Date: Mon, 4 Mar 2024 17:35:09 +0800	[thread overview]
Message-ID: <202403040935.4249Z9qi836647@localhost.localdomain> (raw)
In-Reply-To: <20240304093350.592125-1-mingjinx.ye@intel.com>

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

_Compilation OK_

Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Mon,  4 Mar 2024 09:33:50 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 3408b132b31906fe1ed28d6b2009b98202e1cff0

137877 --> 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-04 10:00 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240304093350.592125-1-mingjinx.ye@intel.com>
2024-03-04  9:35 ` qemudev [this message]
2024-03-04  9:39 ` qemudev
2024-03-04  9:54 ` checkpatch
2024-03-04 10:44 ` 0-day Robot
2024-03-04 11:51 ` |SUCCESS| pw137877 [PATCH] [v4] net/ice: add diagnostic support in T dpdklab
2024-03-04 11:51 ` dpdklab
2024-03-04 11:54 ` dpdklab
2024-03-04 11:54 ` dpdklab
2024-03-04 11:55 ` dpdklab
2024-03-04 11:55 ` dpdklab
2024-03-04 11:56 ` dpdklab
2024-03-04 11:57 ` dpdklab
2024-03-04 11:57 ` dpdklab
2024-03-04 11:57 ` dpdklab
2024-03-04 11:57 ` dpdklab
2024-03-04 11:57 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 11:58 ` dpdklab
2024-03-04 11:59 ` dpdklab
2024-03-04 11:59 ` dpdklab
2024-03-04 11:59 ` dpdklab
2024-03-04 12:12 ` dpdklab
2024-03-04 12:13 ` dpdklab
2024-03-04 12:14 ` dpdklab
2024-03-04 12:14 ` dpdklab
2024-03-04 12:15 ` dpdklab
2024-03-04 12:15 ` dpdklab
2024-03-04 12:15 ` dpdklab
2024-03-04 12:15 ` dpdklab
2024-03-04 12:16 ` dpdklab
2024-03-04 12:16 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:17 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:18 ` dpdklab
2024-03-04 12:19 ` dpdklab
2024-03-04 12:19 ` dpdklab
2024-03-04 12:19 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:20 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:21 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:22 ` dpdklab
2024-03-04 12:23 ` dpdklab
2024-03-04 12:23 ` dpdklab
2024-03-04 12:24 ` dpdklab
2024-03-04 12:52 ` dpdklab
2024-03-04 12:53 ` dpdklab
2024-03-04 13:27 ` dpdklab
2024-03-07 23:09 ` dpdklab
2024-03-07 23:32 ` dpdklab
2024-03-08  0:04 ` 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=202403040935.4249Z9qi836647@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).