From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw153073 [PATCH V2] ethdev_trace.h: Update the trace point function when _TIME_BITS=64
Date: Tue, 22 Apr 2025 19:55:57 +0800 [thread overview]
Message-ID: <202504221155.53MBtv7j1676130@localhost.localdomain> (raw)
In-Reply-To: <20250422122956.1217418-1-changqing.li@windriver.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/153073
_Compilation OK_
Submitter: changqing.li@windriver.com
Date: Tue, 22 Apr 2025 20:29:56 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: e1079be7f8cd78c0952a2b52404814c926dde2a8
153073 --> 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-04-22 12:32 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250422122956.1217418-1-changqing.li@windriver.com>
2025-04-22 11:55 ` qemudev [this message]
2025-04-22 12:00 ` qemudev
2025-04-22 12:30 ` |WARNING| " checkpatch
2025-04-22 18:44 ` |SUCCESS| pw153073 [PATCH] [V2] ethdev_trace.h: Update the trace poi dpdklab
2025-04-22 19:07 ` dpdklab
2025-04-22 19:07 ` dpdklab
2025-04-22 19:15 ` dpdklab
2025-04-22 19:16 ` dpdklab
2025-04-22 19:17 ` dpdklab
2025-04-22 19:22 ` dpdklab
2025-04-22 19:28 ` dpdklab
2025-04-22 19:30 ` dpdklab
2025-04-22 19:32 ` dpdklab
2025-04-22 19:41 ` dpdklab
2025-04-22 19:42 ` dpdklab
2025-04-22 19:44 ` |PENDING| " dpdklab
2025-04-22 19:49 ` |SUCCESS| " dpdklab
2025-04-22 19:50 ` |WARNING| " dpdklab
2025-04-22 19:54 ` |SUCCESS| " dpdklab
2025-04-22 19:54 ` |PENDING| " dpdklab
2025-04-22 19:54 ` |SUCCESS| " dpdklab
2025-04-22 19:55 ` dpdklab
2025-04-22 20:00 ` dpdklab
2025-04-22 20:06 ` dpdklab
2025-04-22 20:10 ` dpdklab
2025-04-22 20:30 ` dpdklab
2025-04-22 20:31 ` |PENDING| " dpdklab
2025-04-22 20:34 ` |SUCCESS| " dpdklab
2025-04-22 20:37 ` dpdklab
2025-04-22 20:44 ` |WARNING| " dpdklab
2025-04-22 20:46 ` |PENDING| " dpdklab
2025-04-22 20:53 ` dpdklab
2025-04-22 20:58 ` |SUCCESS| " dpdklab
2025-04-22 21:00 ` dpdklab
2025-04-22 21:01 ` dpdklab
2025-04-22 21:10 ` |WARNING| " dpdklab
2025-04-22 21:18 ` |SUCCESS| " dpdklab
2025-04-22 21:46 ` dpdklab
2025-04-22 21:52 ` dpdklab
2025-04-22 21:52 ` dpdklab
2025-04-22 21:57 ` dpdklab
2025-04-22 22:06 ` dpdklab
2025-04-22 22:11 ` dpdklab
2025-04-22 22:52 ` dpdklab
2025-04-22 23:14 ` dpdklab
2025-04-22 23:19 ` 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=202504221155.53MBtv7j1676130@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).