automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139989-139990 [PATCH v6 2/2] dts: Change hugepage 'amount' to a different term
Date: Wed, 8 May 2024 00:13:09 +0800	[thread overview]
Message-ID: <202405071613.447GD9As2051210@localhost.localdomain> (raw)
In-Reply-To: <20240507163752.305-3-npratte@iol.unh.edu>

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

_Compilation OK_

Submitter: Nicholas Pratte <npratte@iol.unh.edu>
Date: Tue,  7 May 2024 12:37:51 -0400
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78

139989-139990 --> 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-07 16:40 UTC|newest]

Thread overview: 87+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240507163752.305-3-npratte@iol.unh.edu>
2024-05-07 16:13 ` qemudev [this message]
2024-05-07 16:17 ` qemudev
2024-05-07 16:39 ` |SUCCESS| pw139990 " checkpatch
2024-05-07 17:21 ` |SUCCESS| pw139989-139990 [PATCH] [v6,2/2] dts: Change hugepage 'amo dpdklab
2024-05-07 17:21 ` dpdklab
2024-05-07 17:22 ` dpdklab
2024-05-07 17:22 ` dpdklab
2024-05-07 17:23 ` dpdklab
2024-05-07 17:24 ` dpdklab
2024-05-07 17:28 ` dpdklab
2024-05-07 17:29 ` dpdklab
2024-05-07 17:29 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:30 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:31 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:32 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:33 ` dpdklab
2024-05-07 17:34 ` dpdklab
2024-05-07 17:34 ` dpdklab
2024-05-07 17:37 ` dpdklab
2024-05-07 17:37 ` dpdklab
2024-05-07 17:38 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:39 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:40 ` dpdklab
2024-05-07 17:41 ` dpdklab
2024-05-07 17:41 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:42 ` dpdklab
2024-05-07 17:43 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:44 ` dpdklab
2024-05-07 17:45 ` dpdklab
2024-05-07 17:45 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:46 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:47 ` dpdklab
2024-05-07 17:52 ` dpdklab
2024-05-07 18:09 ` dpdklab
2024-05-07 18:09 ` dpdklab
2024-05-07 18:10 ` dpdklab
2024-05-07 18:10 ` dpdklab
2024-05-07 18:11 ` dpdklab
2024-05-07 18:11 ` dpdklab
2024-05-07 18:12 ` dpdklab
2024-05-07 18:12 ` dpdklab
2024-05-07 18:13 ` dpdklab
2024-05-07 18:13 ` dpdklab
2024-05-07 18:14 ` dpdklab
2024-05-07 18:14 ` dpdklab
2024-05-07 18:15 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:16 ` dpdklab
2024-05-07 18:18 ` dpdklab
2024-05-07 18:20 ` dpdklab
2024-05-07 18:23 ` dpdklab
2024-05-07 18:24 ` dpdklab
2024-05-07 18:36 ` dpdklab
2024-05-07 18:44 ` dpdklab
2024-05-07 18:50 ` 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=202405071613.447GD9As2051210@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).