automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139646-139667 [PATCH v1 22/22] net/ixgbe/base: add support for E610 device
Date: Wed, 24 Apr 2024 20:58:50 +0800	[thread overview]
Message-ID: <202404241258.43OCwotp1338849@localhost.localdomain> (raw)
In-Reply-To: <9dc7b80e7c3542323ab1d0d22ab96a882abb7fff.1713964708.git.anatoly.burakov@intel.com>

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

_Compilation OK_

Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 24 Apr 2024 14:21:35 +0100
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 2ac57ed414af92f0c30a799e1824fd47f86a94b0

139646-139667 --> 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-04-24 13:26 UTC|newest]

Thread overview: 89+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9dc7b80e7c3542323ab1d0d22ab96a882abb7fff.1713964708.git.anatoly.burakov@intel.com>
2024-04-24 12:58 ` qemudev [this message]
2024-04-24 13:03 ` qemudev
2024-04-24 13:27 ` |WARNING| pw139667 " checkpatch
2024-04-24 14:05 ` |SUCCESS| pw139646-139667 [PATCH] [v1,22/22] net/ixgbe/base: add sup dpdklab
2024-04-24 14:05 ` dpdklab
2024-04-24 14:11 ` dpdklab
2024-04-24 14:11 ` dpdklab
2024-04-24 14:12 ` dpdklab
2024-04-24 14:12 ` dpdklab
2024-04-24 14:12 ` dpdklab
2024-04-24 14:12 ` dpdklab
2024-04-24 14:13 ` dpdklab
2024-04-24 14:14 ` dpdklab
2024-04-24 14:16 ` dpdklab
2024-04-24 14:16 ` dpdklab
2024-04-24 14:17 ` dpdklab
2024-04-24 14:17 ` dpdklab
2024-04-24 14:17 ` dpdklab
2024-04-24 14:18 ` dpdklab
2024-04-24 14:18 ` dpdklab
2024-04-24 14:18 ` dpdklab
2024-04-24 14:19 ` dpdklab
2024-04-24 14:19 ` dpdklab
2024-04-24 14:19 ` dpdklab
2024-04-24 14:19 ` dpdklab
2024-04-24 14:20 ` dpdklab
2024-04-24 14:20 ` dpdklab
2024-04-24 14:20 ` dpdklab
2024-04-24 14:20 ` dpdklab
2024-04-24 14:22 ` dpdklab
2024-04-24 14:22 ` dpdklab
2024-04-24 14:22 ` dpdklab
2024-04-24 14:22 ` dpdklab
2024-04-24 14:23 ` dpdklab
2024-04-24 14:23 ` dpdklab
2024-04-24 14:23 ` dpdklab
2024-04-24 14:23 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:24 ` dpdklab
2024-04-24 14:25 ` dpdklab
2024-04-24 14:25 ` |SUCCESS| pw139667 [PATCH v1 22/22] net/ixgbe/base: add support for E610 device 0-day Robot
2024-04-24 14:32 ` |SUCCESS| pw139646-139667 [PATCH] [v1,22/22] net/ixgbe/base: add sup dpdklab
2024-04-24 14:33 ` dpdklab
2024-04-24 14:33 ` dpdklab
2024-04-24 14:33 ` dpdklab
2024-04-24 14:33 ` dpdklab
2024-04-24 14:33 ` dpdklab
2024-04-24 14:34 ` dpdklab
2024-04-24 14:35 ` dpdklab
2024-04-24 14:36 ` dpdklab
2024-04-24 14:36 ` dpdklab
2024-04-24 14:36 ` dpdklab
2024-04-24 14:36 ` dpdklab
2024-04-24 14:36 ` dpdklab
2024-04-24 14:37 ` dpdklab
2024-04-24 14:37 ` dpdklab
2024-04-24 14:37 ` dpdklab
2024-04-24 14:38 ` dpdklab
2024-04-24 14:39 ` dpdklab
2024-04-24 14:39 ` dpdklab
2024-04-24 14:40 ` dpdklab
2024-04-24 14:40 ` dpdklab
2024-04-24 14:41 ` dpdklab
2024-04-24 14:41 ` dpdklab
2024-04-24 14:42 ` dpdklab
2024-04-24 14:44 ` dpdklab
2024-04-24 14:45 ` dpdklab
2024-04-24 14:48 ` dpdklab
2024-04-24 14:52 ` dpdklab
2024-04-24 14:52 ` dpdklab
2024-04-24 14:53 ` dpdklab
2024-04-24 14:53 ` dpdklab
2024-04-24 14:54 ` dpdklab
2024-04-24 14:55 ` dpdklab
2024-04-24 14:58 ` dpdklab
2024-04-24 15:03 ` dpdklab
2024-04-24 15:04 ` dpdklab
2024-04-24 15:07 ` dpdklab
2024-04-24 15:10 ` dpdklab
2024-04-24 15:10 ` dpdklab
2024-04-24 15:14 ` dpdklab
2024-04-24 15:18 ` dpdklab
2024-04-24 15:32 ` dpdklab
2024-04-24 15:32 ` 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=202404241258.43OCwotp1338849@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).