automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124606 [PATCH v2] ethdev: add link speed 400G
Date: Wed, 1 Mar 2023 19:08:04 +0800	[thread overview]
Message-ID: <202303011108.321B841l1065066@localhost.localdomain> (raw)
In-Reply-To: <20230301111642.3059321-1-thomas@monjalon.net>

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

_Compilation OK_

Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Wed,  1 Mar 2023 12:16:42 +0100
DPDK git baseline: Repo:dpdk-next-net
  Branch: main
  CommitID: 4ff773385cdbd525c6e5a10015894fa26c286760

124606 --> 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:[~2023-03-01 11:21 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230301111642.3059321-1-thomas@monjalon.net>
2023-03-01 11:08 ` qemudev [this message]
2023-03-01 11:12 ` qemudev
2023-03-01 11:18 ` checkpatch
2023-03-01 13:39 ` 0-day Robot
2023-03-02  1:52 |SUCCESS| pw124606 [PATCH] [v2] " dpdklab
2023-03-02  2:08 dpdklab
2023-03-02  3:39 dpdklab
2023-03-02  3:43 dpdklab
2023-03-02  3:47 dpdklab
2023-03-02  3:59 dpdklab
2023-03-02  4:00 dpdklab
2023-03-02  4:02 dpdklab
2023-03-02  4:06 dpdklab
2023-03-02  4:12 dpdklab
2023-03-02  4:23 dpdklab
2023-03-02  4:32 dpdklab
2023-03-02  4:46 dpdklab
2023-03-02  4:46 dpdklab
2023-03-02  5:11 dpdklab
2023-03-02  5:18 dpdklab
2023-03-02  5:34 dpdklab
2023-03-02  5:46 dpdklab
2023-03-02  8:38 dpdklab
2023-03-02  8:50 dpdklab
2023-03-02  9:07 dpdklab
2023-03-02  9:19 dpdklab
2023-03-02  9:47 dpdklab
2023-03-02  9:59 dpdklab
2023-03-02 10:11 dpdklab
2023-03-02 10:32 dpdklab
2023-03-02 15:15 dpdklab
2023-03-02 15:42 dpdklab
2023-03-02 20:31 dpdklab
2023-03-02 22:14 dpdklab
2023-03-03 20:43 dpdklab
2023-03-03 21:06 dpdklab
2023-03-03 21:13 dpdklab
2023-03-03 21:15 dpdklab
2023-03-03 21:17 dpdklab
2023-03-03 21:22 dpdklab
2023-03-03 21:28 dpdklab
2023-03-03 21:29 dpdklab
2023-03-03 21:30 dpdklab
2023-03-03 21:31 dpdklab
2023-03-03 21:33 dpdklab
2023-03-03 21:41 dpdklab
2023-03-03 22:00 dpdklab
2023-03-03 22:05 dpdklab
2023-03-03 22:05 dpdklab
2023-03-03 22:06 dpdklab
2023-03-03 22:06 dpdklab
2023-03-03 22:16 dpdklab
2023-03-03 22:17 dpdklab
2023-03-03 22:19 dpdklab
2023-03-03 22:21 dpdklab
2023-03-03 22:22 dpdklab
2023-03-03 22:24 dpdklab
2023-03-03 22:24 dpdklab
2023-03-03 22:26 dpdklab
2023-03-03 23:12 dpdklab
2023-03-03 23:12 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=202303011108.321B841l1065066@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).