automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138848 [PATCH v1] net/i40e: updated 24.03 recommended matching list
Date: Wed, 27 Mar 2024 13:22:58 +0800	[thread overview]
Message-ID: <202403270522.42R5MwIx3340342@localhost.localdomain> (raw)
In-Reply-To: <20240327050655.459332-1-hailinx.xu@intel.com>

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

_Compilation OK_

Submitter: hailinx <hailinx.xu@intel.com>
Date: Wed, 27 Mar 2024 13:06:55 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 2c54ea7a59dfc0a819d3527309c62846fc8853af

138848 --> 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-27  5:47 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240327050655.459332-1-hailinx.xu@intel.com>
2024-03-27  5:22 ` qemudev [this message]
2024-03-27  5:27 ` qemudev
2024-03-27  5:41 ` |WARNING| " checkpatch
2024-03-27  6:45 ` |SUCCESS| " 0-day Robot
2024-03-27  7:33 ` |SUCCESS| pw138848 [PATCH] [v1] net/i40e: updated 24.03 recommended dpdklab
2024-03-27  7:37 ` dpdklab
2024-03-27  7:58 ` dpdklab
2024-03-27  8:00 ` dpdklab
2024-03-27  8:35 ` dpdklab
2024-03-27  8:36 ` dpdklab
2024-03-27  8:37 ` dpdklab
2024-03-27  8:38 ` dpdklab
2024-03-27  8:38 ` dpdklab
2024-03-27  8:39 ` dpdklab
2024-03-27  8:41 ` dpdklab
2024-03-27  8:41 ` dpdklab
2024-03-27  8:42 ` dpdklab
2024-03-27  8:43 ` dpdklab
2024-03-27  8:43 ` dpdklab
2024-03-27  8:48 ` dpdklab
2024-03-27  8:49 ` dpdklab
2024-03-27  8:50 ` dpdklab
2024-03-27  8:50 ` dpdklab
2024-03-27  8:51 ` dpdklab
2024-03-27  8:52 ` dpdklab
2024-03-27  8:53 ` dpdklab
2024-03-27  8:54 ` dpdklab
2024-03-27  8:54 ` dpdklab
2024-03-27  8:56 ` dpdklab
2024-03-27  8:56 ` dpdklab
2024-03-27  8:59 ` dpdklab
2024-03-27  8:59 ` dpdklab
2024-03-27  9:00 ` dpdklab
2024-03-27  9:00 ` dpdklab
2024-03-27  9:01 ` dpdklab
2024-03-27  9:02 ` dpdklab
2024-03-27  9:06 ` dpdklab
2024-03-27  9:06 ` dpdklab
2024-03-27  9:06 ` dpdklab
2024-03-27  9:06 ` dpdklab
2024-03-27  9:07 ` dpdklab
2024-03-27  9:07 ` dpdklab
2024-03-27  9:08 ` dpdklab
2024-03-27  9:09 ` dpdklab
2024-03-27  9:09 ` dpdklab
2024-03-27  9:09 ` dpdklab
2024-03-27  9:10 ` dpdklab
2024-03-27  9:10 ` dpdklab
2024-03-27  9:10 ` dpdklab
2024-03-27  9:11 ` dpdklab
2024-03-27  9:11 ` dpdklab
2024-03-27  9:11 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:12 ` dpdklab
2024-03-27  9:13 ` dpdklab
2024-03-27  9:13 ` dpdklab
2024-03-27  9:13 ` dpdklab
2024-03-27  9:14 ` dpdklab
2024-03-27  9:14 ` dpdklab
2024-03-27  9:14 ` dpdklab
2024-03-27  9:15 ` dpdklab
2024-03-27  9:15 ` dpdklab
2024-03-27  9:16 ` dpdklab
2024-03-27  9:16 ` dpdklab
2024-03-27  9:16 ` dpdklab
2024-03-27  9:17 ` dpdklab
2024-03-27  9:17 ` dpdklab
2024-03-27  9:17 ` dpdklab
2024-03-27  9:17 ` dpdklab
2024-03-27  9:19 ` dpdklab
2024-03-27  9:19 ` dpdklab
2024-03-27  9:19 ` dpdklab
2024-03-27  9:19 ` dpdklab
2024-03-27  9:31 ` |FAILURE| " dpdklab
2024-03-27  9:58 ` dpdklab
2024-03-27 10:11 ` |SUCCESS| " dpdklab
2024-03-27 10:40 ` dpdklab
2024-03-27 11:38 ` dpdklab
2024-03-27 11:45 ` dpdklab
2024-03-27 12:21 ` dpdklab
2024-04-02  6:55 ` dpdklab
2024-04-02  6:59 ` dpdklab
2024-04-02  7:03 ` dpdklab
2024-04-02  7:22 ` dpdklab
2024-04-02  7:26 ` 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=202403270522.42R5MwIx3340342@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).