From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw121684 [PATCH v3 1/1] common/cnxk: add mbox locking
Date: Sat, 7 Jan 2023 01:37:49 +0800 [thread overview]
Message-ID: <202301061737.306HbnK1218416@localhost.localdomain> (raw)
In-Reply-To: <20230106174453.2152659-1-rkudurumalla@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/121684
_Compilation OK_
Submitter: Rakesh Kudurumalla <rkudurumalla@marvell.com>
Date: Fri, 6 Jan 2023 23:14:53 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 6141ebf5fbf3c2ccc4b78ab9491ccb43e570565b
121684 --> 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:[~2023-01-06 17:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230106174453.2152659-1-rkudurumalla@marvell.com>
2023-01-06 17:37 ` qemudev [this message]
2023-01-06 17:41 ` qemudev
2023-01-06 17:45 ` |WARNING| " checkpatch
2023-01-06 18:59 ` |SUCCESS| " 0-day Robot
2023-01-06 18:11 |SUCCESS| pw121684 [PATCH] [v3,1/1] " dpdklab
2023-01-06 18:15 dpdklab
2023-01-06 18:16 dpdklab
2023-01-06 18:17 dpdklab
2023-01-06 18:19 dpdklab
2023-01-06 18:22 dpdklab
2023-01-06 18:25 dpdklab
2023-01-06 18:29 dpdklab
2023-01-06 18:32 dpdklab
2023-01-06 18:58 dpdklab
2023-01-06 19:26 dpdklab
2023-01-06 19:26 dpdklab
2023-01-06 19:26 dpdklab
2023-01-06 19:26 dpdklab
2023-01-06 19:27 dpdklab
2023-01-06 19:36 dpdklab
2023-01-06 19:40 dpdklab
2023-01-06 19:42 dpdklab
2023-01-06 19:44 dpdklab
2023-01-06 19:44 dpdklab
2023-01-06 19:47 dpdklab
2023-01-06 20:28 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=202301061737.306HbnK1218416@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).