From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150456-150457 [PATCH 2/2] dmadev: avoid copies in tracepoints
Date: Fri, 24 Jan 2025 23:55:16 +0800 [thread overview]
Message-ID: <202501241555.50OFtGp33739734@localhost.localdomain> (raw)
In-Reply-To: <20250124161408.310581-2-david.marchand@redhat.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/150457
_Compilation OK_
Submitter: David Marchand <david.marchand@redhat.com>
Date: Fri, 24 Jan 2025 17:14:07 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 5b856206c74bbcf19e12cafa15382a7e15b0a1b5
150456-150457 --> 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:[~2025-01-24 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250124161408.310581-2-david.marchand@redhat.com>
2025-01-24 15:55 ` qemudev [this message]
2025-01-24 15:59 ` qemudev
2025-01-24 16:28 ` |SUCCESS| pw150457 " checkpatch
2025-01-24 17:43 ` 0-day Robot
2025-01-24 19:58 ` |SUCCESS| pw150456-150457 [PATCH] [2/2] dmadev: avoid copies in trac dpdklab
2025-01-24 20:02 ` dpdklab
2025-01-24 20:06 ` dpdklab
2025-01-24 20:14 ` dpdklab
2025-01-24 20:14 ` dpdklab
2025-01-24 20:43 ` dpdklab
2025-01-24 20:53 ` |PENDING| " dpdklab
2025-01-24 21:13 ` dpdklab
2025-01-24 21:16 ` dpdklab
2025-01-24 21:33 ` dpdklab
2025-01-24 22:40 ` |SUCCESS| " dpdklab
2025-01-24 23:22 ` dpdklab
2025-01-24 23:24 ` dpdklab
2025-01-24 23:29 ` dpdklab
2025-01-25 1:01 ` |WARNING| " dpdklab
2025-01-25 1:18 ` dpdklab
2025-01-25 6:46 ` |SUCCESS| " 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=202501241555.50OFtGp33739734@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).