From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143062 [PATCH v4 1/1] examples/l2fwd-jobstats: fix lock availability
Date: Sun, 11 Aug 2024 14:43:08 +0800 [thread overview]
Message-ID: <202408110643.47B6h8r9168289@localhost.localdomain> (raw)
In-Reply-To: <20240811065819.575759-1-rkudurumalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143062
_Compilation OK_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Sun, 11 Aug 2024 12:28:19 +0530
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143062 --> 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-08-11 7:12 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240811065819.575759-1-rkudurumalla@marvell.com>
2024-08-11 6:43 ` qemudev [this message]
2024-08-11 6:47 ` qemudev
2024-08-11 6:59 ` |WARNING| " checkpatch
2024-08-11 8:02 ` |SUCCESS| " 0-day Robot
2024-08-11 8:15 ` |SUCCESS| pw143062 [PATCH] [v4,1/1] examples/l2fwd-jobstats: fix loc dpdklab
2024-08-11 8:15 ` dpdklab
2024-08-11 8:17 ` dpdklab
2024-08-11 8:18 ` dpdklab
2024-08-11 8:20 ` dpdklab
2024-08-11 8:20 ` dpdklab
2024-08-11 8:23 ` dpdklab
2024-08-11 8:25 ` dpdklab
2024-08-11 8:26 ` dpdklab
2024-08-11 8:26 ` dpdklab
2024-08-11 8:31 ` dpdklab
2024-08-11 8:34 ` dpdklab
2024-08-11 8:36 ` dpdklab
2024-08-11 8:39 ` dpdklab
2024-08-11 8:40 ` dpdklab
2024-08-11 8:43 ` |PENDING| " dpdklab
2024-08-11 8:43 ` dpdklab
2024-08-11 8:51 ` |SUCCESS| " dpdklab
2024-08-11 8:51 ` dpdklab
2024-08-11 8:53 ` dpdklab
2024-08-11 8:55 ` |PENDING| " dpdklab
2024-08-11 8:58 ` dpdklab
2024-08-11 9:02 ` |SUCCESS| " dpdklab
2024-08-11 9:03 ` |PENDING| " dpdklab
2024-08-11 9:03 ` dpdklab
2024-08-11 9:03 ` dpdklab
2024-08-11 9:05 ` dpdklab
2024-08-11 9:05 ` dpdklab
2024-08-11 9:05 ` dpdklab
2024-08-11 9:05 ` dpdklab
2024-08-11 9:06 ` dpdklab
2024-08-11 9:09 ` dpdklab
2024-08-11 9:10 ` dpdklab
2024-08-11 9:11 ` dpdklab
2024-08-11 9:12 ` dpdklab
2024-08-11 9:13 ` dpdklab
2024-08-11 9:14 ` dpdklab
2024-08-11 9:15 ` dpdklab
2024-08-11 9:16 ` dpdklab
2024-08-11 9:17 ` dpdklab
2024-08-11 9:18 ` dpdklab
2024-08-11 9:19 ` dpdklab
2024-08-11 9:19 ` dpdklab
2024-08-11 9:19 ` dpdklab
2024-08-11 9:19 ` dpdklab
2024-08-11 9:20 ` dpdklab
2024-08-11 9:21 ` dpdklab
2024-08-11 9:23 ` dpdklab
2024-08-11 9:25 ` dpdklab
2024-08-11 9:25 ` dpdklab
2024-08-11 9:26 ` dpdklab
2024-08-11 9:28 ` dpdklab
2024-08-11 9:28 ` dpdklab
2024-08-11 9:30 ` dpdklab
2024-08-11 9:31 ` dpdklab
2024-08-11 9:31 ` dpdklab
2024-08-11 9:32 ` dpdklab
2024-08-11 9:33 ` dpdklab
2024-08-11 9:34 ` dpdklab
2024-08-11 9:34 ` dpdklab
2024-08-11 9:36 ` dpdklab
2024-08-11 9:37 ` dpdklab
2024-08-11 9:38 ` dpdklab
2024-08-11 9:39 ` dpdklab
2024-08-11 9:41 ` dpdklab
2024-08-11 9:42 ` dpdklab
2024-08-11 9:43 ` dpdklab
2024-08-11 9:43 ` dpdklab
2024-08-11 9:43 ` dpdklab
2024-08-11 9:45 ` dpdklab
2024-08-11 9:46 ` dpdklab
2024-08-11 9:46 ` dpdklab
2024-08-11 9:47 ` dpdklab
2024-08-11 9:48 ` dpdklab
2024-08-11 9:48 ` dpdklab
2024-08-11 9:48 ` dpdklab
2024-08-11 9:49 ` dpdklab
2024-08-11 9:49 ` dpdklab
2024-08-11 9:49 ` dpdklab
2024-08-11 9:50 ` dpdklab
2024-08-11 9:50 ` dpdklab
2024-08-11 9:50 ` dpdklab
2024-08-11 9:51 ` dpdklab
2024-08-11 9:53 ` dpdklab
2024-08-11 9:54 ` dpdklab
2024-08-11 9:55 ` |SUCCESS| " dpdklab
2024-08-11 9:56 ` |PENDING| " dpdklab
2024-08-11 9:56 ` |SUCCESS| " dpdklab
2024-08-11 10:01 ` dpdklab
2024-08-11 10:12 ` dpdklab
2024-08-11 10:17 ` |PENDING| " dpdklab
2024-08-11 11:02 ` dpdklab
2024-08-11 11:12 ` dpdklab
2024-08-11 11:21 ` |SUCCESS| " 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=202408110643.47B6h8r9168289@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).