automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140298 [PATCH v3] net/cpfl: get running host ID for CPFL PMD
Date: Fri, 24 May 2024 11:40:50 +0800	[thread overview]
Message-ID: <202405240340.44O3eohA1955268@localhost.localdomain> (raw)
In-Reply-To: <20240524040553.487093-1-shaiq.wani@intel.com>

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

_Compilation OK_

Submitter: Shaiq Wani <shaiq.wani@intel.com>
Date: Fri, 24 May 2024 04:05:53 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 19be1a0ba8af8a513adb011a3017d583d6312fc9

140298 --> 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-05-24  4:09 UTC|newest]

Thread overview: 90+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240524040553.487093-1-shaiq.wani@intel.com>
2024-05-24  3:40 ` qemudev [this message]
2024-05-24  3:45 ` qemudev
2024-05-24  4:06 ` |WARNING| " checkpatch
2024-05-24  5:04 ` |SUCCESS| " 0-day Robot
2024-05-24  6:20 ` |SUCCESS| pw140298 [PATCH] [v3] net/cpfl: get running host ID for CP dpdklab
2024-05-24  6:21 ` dpdklab
2024-05-24  6:25 ` dpdklab
2024-05-24  6:42 ` dpdklab
2024-05-24  6:49 ` dpdklab
2024-05-24  6:49 ` dpdklab
2024-05-24  6:56 ` dpdklab
2024-05-24  7:08 ` dpdklab
2024-05-24  7:09 ` dpdklab
2024-05-24  7:13 ` dpdklab
2024-05-24  7:13 ` dpdklab
2024-05-24  7:13 ` dpdklab
2024-05-24  7:14 ` dpdklab
2024-05-24  7:14 ` dpdklab
2024-05-24  8:06 ` dpdklab
2024-05-24  8:07 ` dpdklab
2024-05-24  8:10 ` dpdklab
2024-05-24  8:16 ` dpdklab
2024-05-24  8:17 ` dpdklab
2024-05-24  8:21 ` dpdklab
2024-05-24  8:22 ` dpdklab
2024-05-24  8:24 ` dpdklab
2024-05-24  8:28 ` dpdklab
2024-05-24  8:28 ` dpdklab
2024-05-24  8:30 ` dpdklab
2024-05-24  8:30 ` dpdklab
2024-05-24  8:30 ` dpdklab
2024-05-24  8:31 ` dpdklab
2024-05-24  8:32 ` dpdklab
2024-05-24  8:33 ` dpdklab
2024-05-24  8:33 ` dpdklab
2024-05-24  8:35 ` dpdklab
2024-05-24  8:36 ` dpdklab
2024-05-24  8:36 ` dpdklab
2024-05-24  8:38 ` dpdklab
2024-05-24  8:46 ` dpdklab
2024-05-24  8:46 ` dpdklab
2024-05-24  8:47 ` dpdklab
2024-05-24  8:49 ` dpdklab
2024-05-24  8:49 ` dpdklab
2024-05-24  8:50 ` dpdklab
2024-05-24  8:51 ` dpdklab
2024-05-24  8:51 ` dpdklab
2024-05-24  8:52 ` dpdklab
2024-05-24  8:52 ` dpdklab
2024-05-24  8:53 ` dpdklab
2024-05-24  8:54 ` dpdklab
2024-05-24  8:54 ` dpdklab
2024-05-24  8:54 ` dpdklab
2024-05-24  8:55 ` dpdklab
2024-05-24  9:04 ` dpdklab
2024-05-24  9:04 ` dpdklab
2024-05-24  9:06 ` dpdklab
2024-05-24  9:07 ` dpdklab
2024-05-24  9:07 ` dpdklab
2024-05-24  9:08 ` dpdklab
2024-05-24  9:10 ` dpdklab
2024-05-24  9:10 ` dpdklab
2024-05-24  9:10 ` dpdklab
2024-05-24  9:13 ` dpdklab
2024-05-24  9:13 ` dpdklab
2024-05-24  9:14 ` dpdklab
2024-05-24  9:15 ` dpdklab
2024-05-24  9:16 ` dpdklab
2024-05-24  9:17 ` dpdklab
2024-05-24  9:17 ` dpdklab
2024-05-24  9:17 ` dpdklab
2024-05-24  9:19 ` dpdklab
2024-05-24  9:19 ` dpdklab
2024-05-24  9:20 ` dpdklab
2024-05-24  9:21 ` dpdklab
2024-05-24  9:22 ` dpdklab
2024-05-24  9:32 ` dpdklab
2024-05-24  9:32 ` dpdklab
2024-05-24  9:32 ` dpdklab
2024-05-24  9:33 ` dpdklab
2024-05-24  9:33 ` dpdklab
2024-05-24  9:40 ` dpdklab
2024-05-24  9:43 ` dpdklab
2024-05-24  9:46 ` dpdklab
2024-05-24  9:55 ` dpdklab
2024-05-24  9:57 ` dpdklab
2024-05-24 10:04 ` dpdklab
2024-05-24 10:52 ` dpdklab
2024-05-24 10:58 ` dpdklab
2024-05-24 11:10 ` 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=202405240340.44O3eohA1955268@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).