From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125949 [PATCH] dmadev: add tracepoints
Date: Wed, 12 Apr 2023 10:47:07 +0800 [thread overview]
Message-ID: <202304120247.33C2l7qe530217@localhost.localdomain> (raw)
In-Reply-To: <20230412024808.41339-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125949
_Compilation OK_
Submitter: Chengwen Feng <fengchengwen@huawei.com>
Date: Wed, 12 Apr 2023 02:48:08 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 65487b12db83c9ef37526a983c43191cd44dae99
125949 --> 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-12 3:01 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230412024808.41339-1-fengchengwen@huawei.com>
2023-04-12 2:47 ` qemudev [this message]
2023-04-12 2:51 ` qemudev
2023-04-12 2:56 ` |WARNING| " checkpatch
2023-04-12 3:38 ` |SUCCESS| " 0-day Robot
2023-04-12 18:20 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-04-12 18:18 dpdklab
2023-04-12 18:17 dpdklab
2023-04-12 18:17 dpdklab
2023-04-12 18:15 dpdklab
2023-04-12 18:11 dpdklab
2023-04-12 18:06 dpdklab
2023-04-12 17:58 dpdklab
2023-04-12 17:08 dpdklab
2023-04-12 17:07 dpdklab
2023-04-12 17:04 dpdklab
2023-04-12 17:02 dpdklab
2023-04-12 16:53 dpdklab
2023-04-12 16:48 dpdklab
2023-04-12 16:46 dpdklab
2023-04-12 16:45 dpdklab
2023-04-12 16:41 dpdklab
2023-04-12 16:40 dpdklab
2023-04-12 16:37 dpdklab
2023-04-12 16:14 dpdklab
2023-04-12 16:09 dpdklab
2023-04-12 16:04 dpdklab
2023-04-12 15:49 dpdklab
2023-04-12 15:44 dpdklab
2023-04-12 4:36 dpdklab
2023-04-12 4:36 dpdklab
2023-04-12 4:25 dpdklab
2023-04-12 4:19 dpdklab
2023-04-12 4:18 dpdklab
2023-04-12 4:17 dpdklab
2023-04-12 4:13 dpdklab
2023-04-12 4:05 dpdklab
2023-04-12 4:03 dpdklab
2023-04-12 4:02 dpdklab
2023-04-12 3:56 dpdklab
2023-04-12 3:56 dpdklab
2023-04-12 3:54 dpdklab
2023-04-12 3:52 dpdklab
2023-04-12 3:52 dpdklab
2023-04-12 3:51 dpdklab
2023-04-12 3:49 dpdklab
2023-04-12 3:49 dpdklab
2023-04-12 3:46 dpdklab
2023-04-12 3:45 dpdklab
2023-04-12 3:43 dpdklab
2023-04-12 3:42 dpdklab
2023-04-12 3:41 dpdklab
2023-04-12 3:40 dpdklab
2023-04-12 3:39 dpdklab
2023-04-12 3:36 dpdklab
2023-04-12 3:36 dpdklab
2023-04-12 3:34 dpdklab
2023-04-12 3:33 dpdklab
2023-04-12 3:29 dpdklab
2023-04-12 3:27 dpdklab
2023-04-12 3:26 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=202304120247.33C2l7qe530217@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).