automatic DPDK test reports
 help / color / mirror / Atom feed
From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135706 [PATCH] dts: improve documentation
Date: Wed, 3 Jan 2024 20:35:34 +0800	[thread overview]
Message-ID: <202401031235.403CZYM0714406@localhost.localdomain> (raw)
In-Reply-To: <20240103125438.182098-1-Luca.Vizzarro@arm.com>

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

_Compilation OK_

Submitter: Luca Vizzarro <luca.vizzarro@arm.com>
Date: Wed,  3 Jan 2024 12:54:37 +0000
DPDK git baseline: Repo:dpdk
  Branch: main
  CommitID: 6ef07151aac4b4d9601d547f94a996d1c71b3871

135706 --> 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-01-03 12:56 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240103125438.182098-1-Luca.Vizzarro@arm.com>
2024-01-03 12:35 ` qemudev [this message]
2024-01-03 12:39 ` qemudev
2024-01-03 12:55 ` checkpatch
2024-01-03 13:45 ` 0-day Robot
2024-01-03 13:28 dpdklab
2024-01-03 13:29 dpdklab
2024-01-03 13:29 dpdklab
2024-01-03 13:29 dpdklab
2024-01-03 13:30 dpdklab
2024-01-03 13:30 dpdklab
2024-01-03 13:30 dpdklab
2024-01-03 13:30 dpdklab
2024-01-03 13:37 dpdklab
2024-01-03 13:37 dpdklab
2024-01-03 13:39 dpdklab
2024-01-03 13:39 dpdklab
2024-01-03 13:39 dpdklab
2024-01-03 13:40 dpdklab
2024-01-03 13:40 dpdklab
2024-01-03 13:40 dpdklab
2024-01-03 13:40 dpdklab
2024-01-03 13:40 dpdklab
2024-01-03 13:42 dpdklab
2024-01-03 13:42 dpdklab
2024-01-03 13:47 dpdklab
2024-01-03 13:48 dpdklab
2024-01-03 13:48 dpdklab
2024-01-03 13:48 dpdklab
2024-01-03 13:49 dpdklab
2024-01-03 13:50 dpdklab
2024-01-03 13:51 dpdklab
2024-01-03 13:53 dpdklab
2024-01-03 13:55 dpdklab
2024-01-03 13:57 dpdklab
2024-01-03 14:01 dpdklab
2024-01-03 14:02 dpdklab
2024-01-03 14:05 dpdklab
2024-01-03 14:06 dpdklab
2024-01-03 14:08 dpdklab
2024-01-03 14:09 dpdklab
2024-01-03 14:09 dpdklab
2024-01-03 14:09 dpdklab
2024-01-03 14:10 dpdklab
2024-01-03 14:11 dpdklab
2024-01-03 14:11 dpdklab
2024-01-03 14:12 dpdklab
2024-01-03 14:13 dpdklab
2024-01-03 14:13 dpdklab
2024-01-03 14:14 dpdklab
2024-01-03 14:18 dpdklab
2024-01-03 14:20 dpdklab
2024-01-03 14:20 dpdklab
2024-01-03 14:20 dpdklab
2024-01-03 14:20 dpdklab
2024-01-03 14:21 dpdklab
2024-01-03 14:22 dpdklab
2024-01-03 14:23 dpdklab
2024-01-03 14:25 dpdklab
2024-01-03 14:26 dpdklab
2024-01-03 14:26 dpdklab
2024-01-03 14:27 dpdklab
2024-01-03 14:27 dpdklab
2024-01-03 14:27 dpdklab
2024-01-03 14:30 dpdklab
2024-01-03 14:32 dpdklab
2024-01-03 14:40 dpdklab
2024-01-03 15:03 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=202401031235.403CZYM0714406@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).