automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw137814 [PATCH v3] ethdev: add Linux ethtool link mode conversion
Date: Sun, 3 Mar 2024 17:35:36 +0800	[thread overview]
Message-ID: <202403030935.4239ZaUa366745@localhost.localdomain> (raw)
In-Reply-To: <20240303095812.2235050-1-thomas@monjalon.net>

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

_Compilation OK_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Sun,  3 Mar 2024 10:56:44 +0100
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: d4d5bbe6791850987d6d28da675574a868e8274c

137814 --> 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-03 10:00 UTC|newest]

Thread overview: 77+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240303095812.2235050-1-thomas@monjalon.net>
2024-03-03  9:35 ` qemudev [this message]
2024-03-03  9:40 ` qemudev
2024-03-03  9:58 ` checkpatch
2024-03-03 11:04 ` 0-day Robot
2024-03-03 18:48 ` |SUCCESS| pw137814 [PATCH] [v3] ethdev: add Linux ethtool link mode dpdklab
2024-03-03 18:49 ` dpdklab
2024-03-03 18:49 ` dpdklab
2024-03-03 18:54 ` dpdklab
2024-03-03 18:54 ` dpdklab
2024-03-03 18:55 ` dpdklab
2024-03-03 18:55 ` dpdklab
2024-03-03 18:55 ` dpdklab
2024-03-03 18:56 ` dpdklab
2024-03-03 18:56 ` dpdklab
2024-03-03 18:57 ` dpdklab
2024-03-03 18:58 ` dpdklab
2024-03-03 18:59 ` dpdklab
2024-03-03 18:59 ` dpdklab
2024-03-03 19:00 ` dpdklab
2024-03-03 19:00 ` dpdklab
2024-03-03 19:01 ` dpdklab
2024-03-03 19:01 ` dpdklab
2024-03-03 19:02 ` dpdklab
2024-03-03 19:02 ` dpdklab
2024-03-03 19:02 ` dpdklab
2024-03-03 19:03 ` dpdklab
2024-03-03 19:04 ` dpdklab
2024-03-03 19:06 ` dpdklab
2024-03-03 19:07 ` dpdklab
2024-03-03 19:07 ` dpdklab
2024-03-03 19:07 ` dpdklab
2024-03-03 19:08 ` dpdklab
2024-03-03 19:08 ` dpdklab
2024-03-03 19:09 ` dpdklab
2024-03-03 19:09 ` dpdklab
2024-03-03 19:11 ` dpdklab
2024-03-03 19:12 ` dpdklab
2024-03-03 19:14 ` dpdklab
2024-03-03 19:15 ` dpdklab
2024-03-03 19:15 ` dpdklab
2024-03-03 19:17 ` dpdklab
2024-03-03 19:18 ` dpdklab
2024-03-03 19:18 ` dpdklab
2024-03-03 19:19 ` dpdklab
2024-03-03 19:20 ` dpdklab
2024-03-03 19:21 ` dpdklab
2024-03-03 19:22 ` dpdklab
2024-03-03 19:24 ` dpdklab
2024-03-03 19:24 ` dpdklab
2024-03-03 19:24 ` dpdklab
2024-03-03 19:26 ` dpdklab
2024-03-03 19:26 ` dpdklab
2024-03-03 19:27 ` dpdklab
2024-03-03 19:28 ` dpdklab
2024-03-03 19:28 ` dpdklab
2024-03-03 19:28 ` dpdklab
2024-03-03 19:29 ` dpdklab
2024-03-03 19:30 ` dpdklab
2024-03-03 19:30 ` dpdklab
2024-03-03 19:30 ` dpdklab
2024-03-03 19:31 ` dpdklab
2024-03-03 19:32 ` dpdklab
2024-03-03 19:32 ` dpdklab
2024-03-03 19:33 ` dpdklab
2024-03-03 19:33 ` dpdklab
2024-03-03 19:37 ` dpdklab
2024-03-03 19:38 ` dpdklab
2024-03-03 19:39 ` dpdklab
2024-03-03 19:40 ` dpdklab
2024-03-03 19:40 ` dpdklab
2024-03-03 19:46 ` dpdklab
2024-03-03 19:51 ` dpdklab
2024-03-03 19:55 ` dpdklab
2024-03-03 21:51 ` dpdklab
2024-03-07  8:50 ` dpdklab
2024-03-07  9:25 ` dpdklab
2024-03-07 10:14 ` 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=202403030935.4239ZaUa366745@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).