From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135854 [PATCH] dmadev: add tracepoints at data path APIs
Date: Mon, 15 Jan 2024 14:09:37 +0800 [thread overview]
Message-ID: <202401150609.40F69b7n427236@localhost.localdomain> (raw)
In-Reply-To: <20240112102659.42041-1-fengchengwen@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135854
_Compilation OK_
Submitter: fengchengwen <fengchengwen@huawei.com>
Date: Fri, 12 Jan 2024 10:26:59 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: d4af9a82063e4c39568191eaa12955d3ca39581a
135854 --> 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:[~2024-01-15 6:34 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240112102659.42041-1-fengchengwen@huawei.com>
2024-01-12 10:31 ` checkpatch
2024-01-12 11:58 ` 0-day Robot
2024-01-15 6:09 ` qemudev [this message]
2024-01-15 6:14 ` qemudev
2024-01-13 21:18 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2024-01-13 21:10 dpdklab
2024-01-12 14:35 dpdklab
2024-01-12 13:47 dpdklab
2024-01-12 12:32 dpdklab
2024-01-12 12:16 dpdklab
2024-01-12 12:14 dpdklab
2024-01-12 11:55 dpdklab
2024-01-12 11:55 dpdklab
2024-01-12 11:54 dpdklab
2024-01-12 11:54 dpdklab
2024-01-12 11:52 dpdklab
2024-01-12 11:51 dpdklab
2024-01-12 11:50 dpdklab
2024-01-12 11:48 dpdklab
2024-01-12 11:48 dpdklab
2024-01-12 11:47 dpdklab
2024-01-12 11:47 dpdklab
2024-01-12 11:47 dpdklab
2024-01-12 11:47 dpdklab
2024-01-12 11:46 dpdklab
2024-01-12 11:46 dpdklab
2024-01-12 11:46 dpdklab
2024-01-12 11:35 dpdklab
2024-01-12 11:31 dpdklab
2024-01-12 11:30 dpdklab
2024-01-12 11:30 dpdklab
2024-01-12 11:30 dpdklab
2024-01-12 11:28 dpdklab
2024-01-12 11:28 dpdklab
2024-01-12 11:27 dpdklab
2024-01-12 11:27 dpdklab
2024-01-12 11:27 dpdklab
2024-01-12 11:27 dpdklab
2024-01-12 11:26 dpdklab
2024-01-12 11:26 dpdklab
2024-01-12 11:26 dpdklab
2024-01-12 11:26 dpdklab
2024-01-12 11:26 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:25 dpdklab
2024-01-12 11:24 dpdklab
2024-01-12 11:24 dpdklab
2024-01-12 11:24 dpdklab
2024-01-12 11:24 dpdklab
2024-01-12 11:24 dpdklab
2024-01-12 11:23 dpdklab
2024-01-12 11:23 dpdklab
2024-01-12 11:22 dpdklab
2024-01-12 11:21 dpdklab
2024-01-12 11:20 dpdklab
2024-01-12 11:18 dpdklab
2024-01-12 11:15 dpdklab
2024-01-12 11:14 dpdklab
2024-01-12 11:13 dpdklab
2024-01-12 11:13 dpdklab
2024-01-12 11:13 dpdklab
2024-01-12 11:12 dpdklab
2024-01-12 11:12 dpdklab
2024-01-12 11:12 dpdklab
2024-01-12 11:12 dpdklab
2024-01-12 11:12 dpdklab
2024-01-12 11:11 dpdklab
2024-01-12 11:11 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=202401150609.40F69b7n427236@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).