From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125038-125049 [PATCH v6 12/12] app/mldev: add documentation for mldev test cases
Date: Sat, 11 Mar 2023 23:02:08 +0800 [thread overview]
Message-ID: <202303111502.32BF28fm4017033@localhost.localdomain> (raw)
In-Reply-To: <20230311150905.26824-13-syalavarthi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125049
_Compilation OK_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Sat, 11 Mar 2023 07:08:54 -0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 0fd1386c30c3ad9365d7fdd2829bf7cb2e1b9dff
125038-125049 --> 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
next parent reply other threads:[~2023-03-11 15:16 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230311150905.26824-13-syalavarthi@marvell.com>
2023-03-11 15:02 ` qemudev [this message]
2023-03-11 15:06 ` qemudev
2023-03-11 15:13 ` |WARNING| pw125049 " checkpatch
2023-03-11 17:19 ` |SUCCESS| " 0-day Robot
2023-03-11 17:40 |SUCCESS| pw125038-125049 [PATCH] [v6, " dpdklab
2023-03-11 17:50 dpdklab
2023-03-11 17:51 dpdklab
2023-03-11 17:52 dpdklab
2023-03-11 17:52 dpdklab
2023-03-11 17:54 dpdklab
2023-03-11 17:57 dpdklab
2023-03-11 17:59 dpdklab
2023-03-11 17:59 dpdklab
2023-03-11 18:01 dpdklab
2023-03-11 18:02 dpdklab
2023-03-11 18:07 dpdklab
2023-03-11 18:11 dpdklab
2023-03-11 18:22 dpdklab
2023-03-11 18:28 dpdklab
2023-03-11 18:32 dpdklab
2023-03-11 18:33 dpdklab
2023-03-11 18:35 dpdklab
2023-03-11 18:35 dpdklab
2023-03-11 18:36 dpdklab
2023-03-11 18:39 dpdklab
2023-03-11 18:39 dpdklab
2023-03-11 18:41 dpdklab
2023-03-11 18:42 dpdklab
2023-03-11 18:44 dpdklab
2023-03-11 18:49 dpdklab
2023-03-11 18:54 dpdklab
2023-03-11 19:40 dpdklab
2023-03-12 12:55 dpdklab
2023-03-12 13:11 dpdklab
2023-03-12 13:14 dpdklab
2023-03-12 14:08 dpdklab
2023-03-12 23:12 dpdklab
2023-03-12 23:19 dpdklab
2023-03-12 23:20 dpdklab
2023-03-12 23:24 dpdklab
2023-03-12 23:26 dpdklab
2023-03-12 23:30 dpdklab
2023-03-12 23:36 dpdklab
2023-03-12 23:37 dpdklab
2023-03-12 23:41 dpdklab
2023-03-12 23:45 dpdklab
2023-03-12 23:46 dpdklab
2023-03-12 23:48 dpdklab
2023-03-13 0:24 dpdklab
2023-03-13 0:25 dpdklab
2023-03-13 0:34 dpdklab
2023-03-13 0:36 dpdklab
2023-03-13 0:37 dpdklab
2023-03-13 0:37 dpdklab
2023-03-13 0:37 dpdklab
2023-03-13 0:43 dpdklab
2023-03-13 1:01 dpdklab
2023-03-13 1:10 dpdklab
2023-03-13 1:12 dpdklab
2023-03-13 1:13 dpdklab
2023-03-13 1:14 dpdklab
2023-03-13 1:22 dpdklab
2023-03-13 1:27 dpdklab
2023-03-13 1:27 dpdklab
2023-03-13 16:42 dpdklab
2023-03-13 18:06 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=202303111502.32BF28fm4017033@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).