automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138409 [PATCH] net/igc: fix disabling timesync
Date: Fri, 15 Mar 2024 08:57:13 +0800	[thread overview]
Message-ID: <202403150057.42F0vDno1394678@localhost.localdomain> (raw)
In-Reply-To: <20240315010631.1374624-1-wenwux.ma@intel.com>

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

_Compilation OK_

Submitter: Wenwu Ma <wenwux.ma@intel.com>
Date: Fri, 15 Mar 2024 09:06:31 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
  Branch: main
  CommitID: 19082c1fac430c74bb4b1c101edd12d88928e7c2

138409 --> 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-15  1:22 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240315010631.1374624-1-wenwux.ma@intel.com>
2024-03-15  0:57 ` qemudev [this message]
2024-03-15  1:01 ` qemudev
2024-03-15  1:19 ` checkpatch
2024-03-15  1:56 ` dpdklab
2024-03-15  1:56 ` dpdklab
2024-03-15  1:56 ` dpdklab
2024-03-15  1:57 ` dpdklab
2024-03-15  1:57 ` dpdklab
2024-03-15  1:58 ` dpdklab
2024-03-15  1:58 ` dpdklab
2024-03-15  1:58 ` dpdklab
2024-03-15  1:59 ` dpdklab
2024-03-15  1:59 ` dpdklab
2024-03-15  2:00 ` dpdklab
2024-03-15  2:00 ` dpdklab
2024-03-15  2:00 ` dpdklab
2024-03-15  2:01 ` dpdklab
2024-03-15  2:01 ` dpdklab
2024-03-15  2:01 ` dpdklab
2024-03-15  2:02 ` dpdklab
2024-03-15  2:02 ` dpdklab
2024-03-15  2:02 ` dpdklab
2024-03-15  2:03 ` dpdklab
2024-03-15  2:03 ` dpdklab
2024-03-15  2:03 ` dpdklab
2024-03-15  2:03 ` dpdklab
2024-03-15  2:03 ` dpdklab
2024-03-15  2:04 ` dpdklab
2024-03-15  2:04 ` dpdklab
2024-03-15  2:04 ` dpdklab
2024-03-15  2:04 ` dpdklab
2024-03-15  2:04 ` dpdklab
2024-03-15  2:05 ` dpdklab
2024-03-15  2:05 ` dpdklab
2024-03-15  2:05 ` dpdklab
2024-03-15  2:05 ` dpdklab
2024-03-15  2:06 ` dpdklab
2024-03-15  2:06 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:07 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:08 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:09 ` dpdklab
2024-03-15  2:10 ` dpdklab
2024-03-15  2:10 ` dpdklab
2024-03-15  2:10 ` dpdklab
2024-03-15  2:11 ` dpdklab
2024-03-15  2:13 ` dpdklab
2024-03-15  2:13 ` dpdklab
2024-03-15  2:13 ` dpdklab
2024-03-15  2:14 ` dpdklab
2024-03-15  2:16 ` dpdklab
2024-03-15  2:16 ` dpdklab
2024-03-15  2:19 ` dpdklab
2024-03-15  2:22 ` dpdklab
2024-03-15  2:23 ` dpdklab
2024-03-15  2:27 ` dpdklab
2024-03-15  3:16 ` dpdklab
2024-03-15  4:23 ` 0-day Robot
2024-03-18 16:32 ` dpdklab
2024-03-18 17:08 ` 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=202403150057.42F0vDno1394678@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).