From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148412-148413 [PATCH 2/2] examples/l2fwd-event: fix spinlock handling
Date: Wed, 13 Nov 2024 23:43:41 +0800 [thread overview]
Message-ID: <202411131543.4ADFhf1M2981615@localhost.localdomain> (raw)
In-Reply-To: <20241113161455.2649551-2-hemant.agrawal@nxp.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148413
_Compilation OK_
Submitter: Hemant Agrawal <hemant.agrawal@nxp.com>
Date: Wed, 13 Nov 2024 21:44:54 +0530
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 012b02bdbc95a5ec3b293f2d37d8955140fd8831
148412-148413 --> 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-11-13 16:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241113161455.2649551-2-hemant.agrawal@nxp.com>
2024-11-13 15:43 ` qemudev [this message]
2024-11-13 15:48 ` qemudev
2024-11-13 16:16 ` |SUCCESS| pw148413 " checkpatch
2024-11-13 17:05 ` 0-day Robot
2024-11-13 23:00 ` |SUCCESS| pw148412-148413 [PATCH] [2/2] examples/l2fwd-event: fix sp dpdklab
2024-11-13 23:04 ` dpdklab
2024-11-13 23:27 ` dpdklab
2024-11-14 0:06 ` dpdklab
2024-11-14 0:42 ` |PENDING| " dpdklab
2024-11-14 0:42 ` dpdklab
2024-11-14 1:01 ` |SUCCESS| " dpdklab
2024-11-14 1:29 ` dpdklab
2024-11-14 1:59 ` dpdklab
2024-11-14 2:40 ` |PENDING| " dpdklab
2024-11-14 3:09 ` dpdklab
2024-11-14 4:21 ` |SUCCESS| " dpdklab
2024-11-14 4:48 ` dpdklab
2024-11-14 6:40 ` dpdklab
2024-11-14 7:09 ` dpdklab
2024-11-14 7:35 ` dpdklab
2024-11-14 9:55 ` 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=202411131543.4ADFhf1M2981615@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).