From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126075 [PATCH v2] dmadev: add tracepoints
Date: Fri, 14 Apr 2023 17:07:08 +0800 [thread overview]
Message-ID: <202304140907.33E978lR974546@localhost.localdomain> (raw)
In-Reply-To: <20230414090901.32164-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126075
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Fri, 14 Apr 2023 09:09:01 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126075 --> 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-04-14 9:21 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230414090901.32164-1-fengchengwen@huawei.com>
2023-04-14 9:07 ` qemudev [this message]
2023-04-14 9:11 ` qemudev
2023-04-14 9:17 ` |WARNING| " checkpatch
2023-04-14 10:39 ` |SUCCESS| " 0-day Robot
2023-04-14 12:16 |SUCCESS| pw126075 [PATCH] [v2] " dpdklab
2023-04-14 12:19 dpdklab
2023-04-14 12:23 dpdklab
2023-04-14 12:23 dpdklab
2023-04-14 12:25 dpdklab
2023-04-14 12:26 dpdklab
2023-04-14 12:30 dpdklab
2023-04-14 12:31 dpdklab
2023-04-14 12:39 dpdklab
2023-04-14 12:42 dpdklab
2023-04-14 12:45 dpdklab
2023-04-14 12:53 dpdklab
2023-04-14 13:00 dpdklab
2023-04-14 13:01 dpdklab
2023-04-14 13:05 dpdklab
2023-04-14 13:05 dpdklab
2023-04-14 13:05 dpdklab
2023-04-14 13:05 dpdklab
2023-04-14 13:07 dpdklab
2023-04-14 13:08 dpdklab
2023-04-14 13:08 dpdklab
2023-04-14 13:13 dpdklab
2023-04-14 13:15 dpdklab
2023-04-14 13:16 dpdklab
2023-04-14 13:21 dpdklab
2023-04-14 13:25 dpdklab
2023-04-14 13:26 dpdklab
2023-04-14 13:35 dpdklab
2023-04-14 13:39 dpdklab
2023-04-14 13:45 dpdklab
2023-04-14 13:46 dpdklab
2023-04-14 13:49 dpdklab
2023-04-14 13:58 dpdklab
2023-04-14 13:59 dpdklab
2023-04-14 14:14 dpdklab
2023-04-14 14:18 dpdklab
2023-04-14 14:23 dpdklab
2023-04-14 14:24 dpdklab
2023-04-14 14:28 dpdklab
2023-04-14 14:33 dpdklab
2023-04-14 15:19 dpdklab
2023-04-14 15:27 dpdklab
2023-04-14 17:00 dpdklab
2023-04-14 18:49 dpdklab
2023-04-14 18:50 dpdklab
2023-04-14 18:56 dpdklab
2023-04-14 20:28 dpdklab
2023-04-14 20:29 dpdklab
2023-04-15 0:12 dpdklab
2023-04-15 0:16 dpdklab
2023-04-15 0:21 dpdklab
2023-04-15 0:37 dpdklab
2023-04-15 0:41 dpdklab
2023-04-15 0:46 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=202304140907.33E978lR974546@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).