From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144857-144862 [PATCH v4 6/6] examples: use eventdev pre-scheduling
Date: Tue, 1 Oct 2024 20:52:47 +0800 [thread overview]
Message-ID: <202410011252.491CqldT1738594@localhost.localdomain> (raw)
In-Reply-To: <20241001131901.7920-7-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144862
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tue, 1 Oct 2024 18:48:56 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: bf0ff8df59c7e32f95c0b542cc4a7918f8a3da84
144857-144862 --> 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-10-01 13:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241001131901.7920-7-pbhagavatula@marvell.com>
2024-10-01 12:52 ` qemudev [this message]
2024-10-01 12:57 ` qemudev
2024-10-01 13:21 ` |SUCCESS| pw144862 " checkpatch
2024-10-01 14:25 ` 0-day Robot
2024-10-01 17:11 ` |SUCCESS| pw144857-144862 [PATCH] [v4,6/6] examples: use eventdev pr dpdklab
2024-10-01 17:17 ` dpdklab
2024-10-01 17:20 ` dpdklab
2024-10-01 17:22 ` dpdklab
2024-10-01 17:23 ` |PENDING| " dpdklab
2024-10-01 17:27 ` |SUCCESS| " dpdklab
2024-10-01 18:01 ` |PENDING| " dpdklab
2024-10-01 18:04 ` |SUCCESS| " dpdklab
2024-10-01 18:44 ` |PENDING| " dpdklab
2024-10-01 19:22 ` |SUCCESS| " dpdklab
2024-10-01 20:36 ` dpdklab
2024-10-01 21:37 ` |PENDING| " dpdklab
2024-10-01 23:15 ` |SUCCESS| " dpdklab
2024-10-01 23:34 ` dpdklab
2024-10-01 23:40 ` dpdklab
2024-10-02 1:36 ` dpdklab
2024-10-02 1:51 ` dpdklab
2024-10-02 2:38 ` dpdklab
2024-10-02 2:43 ` 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=202410011252.491CqldT1738594@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).