From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146610 [PATCH] event/cnxk: fix getwork write data on reconfig
Date: Tue, 22 Oct 2024 20:01:17 +0800 [thread overview]
Message-ID: <202410221201.49MC1Hbe2677902@localhost.localdomain> (raw)
In-Reply-To: <20241022122339.18255-1-pbhagavatula@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/146610
_Compilation OK_
Submitter: Pavan Nikhilesh Bhagavatula <pbhagavatula@marvell.com>
Date: Tue, 22 Oct 2024 17:53:39 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: e609858b480ca0d646e5f05f2c7fd6bbf35a4140
146610 --> 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-22 12:34 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241022122339.18255-1-pbhagavatula@marvell.com>
2024-10-22 12:01 ` qemudev [this message]
2024-10-22 12:05 ` qemudev
2024-10-22 12:25 ` checkpatch
2024-10-22 13:24 ` 0-day Robot
2024-10-23 4:10 ` |SUCCESS| pw146610 [PATCH] event/cnxk: fix getwork write data on rec dpdklab
2024-10-23 4:24 ` dpdklab
2024-10-23 4:56 ` dpdklab
2024-10-23 5:13 ` dpdklab
2024-10-23 5:24 ` dpdklab
2024-10-23 5:30 ` dpdklab
2024-10-23 5:41 ` dpdklab
2024-10-23 5:44 ` dpdklab
2024-10-23 6:02 ` dpdklab
2024-10-23 6:20 ` dpdklab
2024-10-23 7:02 ` dpdklab
2024-10-23 7:38 ` dpdklab
2024-10-23 7:57 ` dpdklab
2024-10-23 8:34 ` dpdklab
2024-10-24 5:41 ` dpdklab
2024-10-24 5:50 ` |PENDING| " dpdklab
2024-10-24 5:58 ` |SUCCESS| " dpdklab
2024-10-24 6:25 ` |WARNING| " dpdklab
2024-10-24 6:36 ` |SUCCESS| " dpdklab
2024-10-24 6:37 ` 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=202410221201.49MC1Hbe2677902@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).