From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144266 [PATCH v2] ethdev: optimize the activation of fast-path tracepoints
Date: Thu, 19 Sep 2024 00:03:32 +0800 [thread overview]
Message-ID: <202409181603.48IG3W4p3414445@localhost.localdomain> (raw)
In-Reply-To: <20240918162750.116243-1-adel.belkhiri@gmail.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144266
_Compilation OK_
Submitter: Adel Belkhiri <adel.belkhiri@gmail.com>
Date: Wed, 18 Sep 2024 12:27:50 -0400
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 523fd7b3adfdf5a87651e8ca33bc69223b3211d5
144266 --> 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:[~2024-09-18 16:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240918162750.116243-1-adel.belkhiri@gmail.com>
2024-09-18 16:03 ` qemudev [this message]
2024-09-18 16:08 ` qemudev
2024-09-18 16:30 ` |WARNING| " checkpatch
2024-09-18 17:24 ` |FAILURE| " 0-day Robot
2024-09-18 19:55 ` |SUCCESS| pw144266 [PATCH] [v2] ethdev: optimize the activation of f dpdklab
2024-09-18 19:56 ` dpdklab
2024-09-18 20:08 ` dpdklab
2024-09-18 20:54 ` |PENDING| " dpdklab
2024-09-18 21:01 ` |SUCCESS| " dpdklab
2024-09-18 21:46 ` |PENDING| " dpdklab
2024-09-18 22:15 ` |SUCCESS| " dpdklab
2024-09-18 22:17 ` dpdklab
2024-09-18 22:47 ` dpdklab
2024-09-18 22:59 ` dpdklab
2024-09-18 23:18 ` |PENDING| " dpdklab
2024-09-18 23:18 ` |SUCCESS| " dpdklab
2024-09-18 23:45 ` dpdklab
2024-09-19 0:39 ` dpdklab
2024-09-19 1:46 ` dpdklab
2024-09-19 4:31 ` dpdklab
2024-09-20 2:48 ` dpdklab
2024-09-22 18:10 ` dpdklab
2024-09-22 18:21 ` 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=202409181603.48IG3W4p3414445@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).