automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139184 [PATCH] config/arm: add Ampere AmpereOneX platform
Date: Mon, 8 Apr 2024 16:06:01 +0800	[thread overview]
Message-ID: <202404080806.438861db3843762@localhost.localdomain> (raw)
In-Reply-To: <20240407063604.79303-1-jiangyutang@os.amperecomputing.com>

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

_Compilation OK_

Submitter: Yutang Jiang <jiangyutang@os.amperecomputing.com>
Date: Sun,  7 Apr 2024 02:36:04 -0400
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: e2e546ab5bf5e024986ccb5310ab43982f3bb40c

139184 --> 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-08  8:31 UTC|newest]

Thread overview: 86+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240407063604.79303-1-jiangyutang@os.amperecomputing.com>
2024-04-08  8:06 ` qemudev [this message]
2024-04-08  8:10 ` qemudev
2024-04-08  8:29 ` |WARNING| " checkpatch
2024-04-08 13:11 ` |SUCCESS| pw139184 [PATCH] config/arm: add Ampere AmpereOneX platfor dpdklab
2024-04-08 13:12 ` dpdklab
2024-04-08 13:12 ` dpdklab
2024-04-08 13:12 ` dpdklab
2024-04-08 13:12 ` dpdklab
2024-04-08 13:12 ` dpdklab
2024-04-08 13:13 ` dpdklab
2024-04-08 13:13 ` dpdklab
2024-04-08 13:13 ` dpdklab
2024-04-08 13:13 ` dpdklab
2024-04-08 13:13 ` dpdklab
2024-04-08 13:14 ` dpdklab
2024-04-08 13:14 ` dpdklab
2024-04-08 13:14 ` dpdklab
2024-04-08 13:15 ` dpdklab
2024-04-08 13:15 ` dpdklab
2024-04-08 13:15 ` dpdklab
2024-04-08 13:16 ` dpdklab
2024-04-08 13:16 ` dpdklab
2024-04-08 13:16 ` dpdklab
2024-04-08 13:16 ` dpdklab
2024-04-08 13:17 ` dpdklab
2024-04-08 13:17 ` dpdklab
2024-04-08 13:17 ` dpdklab
2024-04-08 13:17 ` dpdklab
2024-04-08 13:17 ` dpdklab
2024-04-08 13:18 ` dpdklab
2024-04-08 13:18 ` dpdklab
2024-04-08 13:18 ` dpdklab
2024-04-08 13:18 ` dpdklab
2024-04-08 13:19 ` dpdklab
2024-04-08 13:19 ` dpdklab
2024-04-08 13:19 ` dpdklab
2024-04-08 13:20 ` dpdklab
2024-04-08 13:20 ` dpdklab
2024-04-08 13:20 ` dpdklab
2024-04-08 13:21 ` dpdklab
2024-04-08 13:21 ` dpdklab
2024-04-08 13:22 ` dpdklab
2024-04-08 13:22 ` dpdklab
2024-04-08 13:23 ` dpdklab
2024-04-08 13:23 ` dpdklab
2024-04-08 13:24 ` dpdklab
2024-04-08 13:24 ` dpdklab
2024-04-08 13:24 ` dpdklab
2024-04-08 13:25 ` dpdklab
2024-04-08 13:25 ` dpdklab
2024-04-08 13:25 ` dpdklab
2024-04-08 13:26 ` dpdklab
2024-04-08 13:26 ` dpdklab
2024-04-08 13:27 ` dpdklab
2024-04-08 13:27 ` dpdklab
2024-04-08 13:27 ` dpdklab
2024-04-08 13:27 ` dpdklab
2024-04-08 13:28 ` dpdklab
2024-04-08 13:28 ` dpdklab
2024-04-08 13:28 ` dpdklab
2024-04-08 13:29 ` dpdklab
2024-04-08 13:29 ` dpdklab
2024-04-08 13:29 ` dpdklab
2024-04-08 13:30 ` dpdklab
2024-04-08 13:30 ` dpdklab
2024-04-08 13:31 ` dpdklab
2024-04-08 13:32 ` dpdklab
2024-04-08 13:32 ` dpdklab
2024-04-08 13:32 ` dpdklab
2024-04-08 13:32 ` dpdklab
2024-04-08 13:33 ` dpdklab
2024-04-08 13:34 ` dpdklab
2024-04-08 13:35 ` dpdklab
2024-04-08 13:37 ` dpdklab
2024-04-08 13:38 ` dpdklab
2024-04-08 13:38 ` dpdklab
2024-04-08 13:39 ` dpdklab
2024-04-08 13:41 ` dpdklab
2024-04-08 13:43 ` dpdklab
2024-04-08 13:47 ` dpdklab
2024-04-08 13:54 ` dpdklab
2024-04-08 14:07 ` dpdklab
2024-04-08 14:07 ` dpdklab
2024-04-08 14:09 ` dpdklab
2024-04-08 14:24 ` dpdklab
2024-04-08 15:52 ` 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=202404080806.438861db3843762@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).