From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125200-125209 [PATCH v7 11/11] app/mldev: enable reporting stats in mldev app
Date: Fri, 17 Mar 2023 05:05:08 +0800 [thread overview]
Message-ID: <202303162105.32GL580n761763@localhost.localdomain> (raw)
In-Reply-To: <20230316211434.13409-12-syalavarthi@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125209
_Compilation OK_
Submitter: Srikanth Yalavarthi <syalavarthi@marvell.com>
Date: Thu, 16 Mar 2023 14:14:24 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: bb1f2f5b181b9d8ea7fb28ca2024914fc57bd823
125200-125209 --> 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-16 21:19 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230316211434.13409-12-syalavarthi@marvell.com>
2023-03-16 21:05 ` qemudev [this message]
2023-03-16 21:09 ` qemudev
2023-03-16 21:18 ` |WARNING| pw125209 " checkpatch
2023-03-16 23:19 ` |SUCCESS| " 0-day Robot
2023-03-19 16:52 |SUCCESS| pw125200-125209 [PATCH] [v7, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-03-19 16:51 dpdklab
2023-03-19 16:46 dpdklab
2023-03-19 16:45 dpdklab
2023-03-19 16:43 dpdklab
2023-03-19 16:36 dpdklab
2023-03-19 16:34 dpdklab
2023-03-19 16:31 dpdklab
2023-03-19 16:27 dpdklab
2023-03-19 16:18 dpdklab
2023-03-19 16:16 dpdklab
2023-03-19 16:15 dpdklab
2023-03-19 16:07 dpdklab
2023-03-19 16:00 dpdklab
2023-03-19 16:00 dpdklab
2023-03-19 15:58 dpdklab
2023-03-19 15:58 dpdklab
2023-03-19 15:51 dpdklab
2023-03-19 15:42 dpdklab
2023-03-19 15:42 dpdklab
2023-03-19 15:37 dpdklab
2023-03-19 15:33 dpdklab
2023-03-19 15:26 dpdklab
2023-03-19 15:26 dpdklab
2023-03-19 15:24 dpdklab
2023-03-19 15:17 dpdklab
2023-03-19 15:10 dpdklab
2023-03-19 14:20 dpdklab
2023-03-19 6:18 dpdklab
2023-03-19 5:38 dpdklab
2023-03-19 1:31 dpdklab
2023-03-19 1:27 dpdklab
2023-03-17 4:05 dpdklab
2023-03-17 4:05 dpdklab
2023-03-17 2:42 dpdklab
2023-03-17 2:37 dpdklab
2023-03-17 2:28 dpdklab
2023-03-17 2:14 dpdklab
2023-03-17 1:54 dpdklab
2023-03-17 1:41 dpdklab
2023-03-17 0:42 dpdklab
2023-03-17 0:29 dpdklab
2023-03-17 0:12 dpdklab
2023-03-16 23:59 dpdklab
2023-03-16 23:24 dpdklab
2023-03-16 23:19 dpdklab
2023-03-16 23:14 dpdklab
2023-03-16 23:00 dpdklab
2023-03-16 22:59 dpdklab
2023-03-16 22:54 dpdklab
2023-03-16 22:52 dpdklab
2023-03-16 22:52 dpdklab
2023-03-16 22:50 dpdklab
2023-03-16 22:39 dpdklab
2023-03-16 22:26 dpdklab
2023-03-16 22:25 dpdklab
2023-03-16 22:19 dpdklab
2023-03-16 22:13 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=202303162105.32GL580n761763@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).