From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw123163-123174 [PATCH v2 12/12] mldev: support to get debug info and test device
Date: Tue, 7 Feb 2023 04:42:18 +0800 [thread overview]
Message-ID: <202302062042.316KgIiv3663913@localhost.localdomain> (raw)
In-Reply-To: <20230206202453.336280-13-jerinj@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/123174
_Compilation OK_
Submitter: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
Date: Tue, 7 Feb 2023 01:54:42 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 47b9fb64c15d60e1c8c2c8f6e63824fd2cada428
123163-123174 --> 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 prev parent reply other threads:[~2023-02-06 20:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230206202453.336280-13-jerinj@marvell.com>
2023-02-06 20:28 ` |SUCCESS| pw123174 " checkpatch
2023-02-06 20:42 ` qemudev [this message]
2023-02-06 20:46 ` |SUCCESS| pw123163-123174 " qemudev
2023-02-06 21:19 ` |SUCCESS| pw123174 [dpdk-dev] " 0-day Robot
2023-02-07 15:08 |SUCCESS| pw123163-123174 [PATCH] [v2, " dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-02-07 12:59 dpdklab
2023-02-07 9:45 dpdklab
2023-02-07 5:40 dpdklab
2023-02-07 5:40 dpdklab
2023-02-07 4:24 dpdklab
2023-02-06 22:00 dpdklab
2023-02-06 21:11 dpdklab
2023-02-06 21:07 dpdklab
2023-02-06 21:04 dpdklab
2023-02-06 21:02 dpdklab
2023-02-06 20:58 dpdklab
2023-02-06 20:57 dpdklab
2023-02-06 20:52 dpdklab
2023-02-06 20:52 dpdklab
2023-02-06 20:51 dpdklab
2023-02-06 20:50 dpdklab
2023-02-06 20:47 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=202302062042.316KgIiv3663913@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).