From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw130499 [PATCH ] common/cnxk: fix ROC naming convention
Date: Fri, 18 Aug 2023 11:49:36 +0800 [thread overview]
Message-ID: <202308180349.37I3naYn3432748@localhost.localdomain> (raw)
In-Reply-To: <20230818040139.626967-1-psatheesh@marvell.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/130499
_Compilation OK_
Submitter: Satheesh Paul Antonysamy <psatheesh@marvell.com>
Date: Fri, 18 Aug 2023 09:31:39 +0530
DPDK git baseline: Repo:dpdk-next-net-mrvl
Branch: for-next-net
CommitID: 67196a9c023e18168b3c58d8b379235be7337e0f
130499 --> 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-08-18 4:03 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230818040139.626967-1-psatheesh@marvell.com>
2023-08-18 3:49 ` qemudev [this message]
2023-08-18 3:53 ` qemudev
2023-08-18 4:02 ` checkpatch
2023-08-18 10:16 |SUCCESS| pw130499 [PATCH] " dpdklab
2023-08-18 10:24 dpdklab
2023-08-18 10:25 dpdklab
2023-08-18 10:26 dpdklab
2023-08-18 10:27 dpdklab
2023-08-18 10:30 dpdklab
2023-08-18 10:30 dpdklab
2023-08-18 10:33 dpdklab
2023-08-18 10:36 dpdklab
2023-08-18 10:41 dpdklab
2023-08-18 10:44 dpdklab
2023-08-18 10:46 dpdklab
2023-08-18 10:47 dpdklab
2023-08-18 10:49 dpdklab
2023-08-18 10:50 dpdklab
2023-08-18 10:57 dpdklab
2023-08-18 10:58 dpdklab
2023-08-18 10:59 dpdklab
2023-08-18 11:02 dpdklab
2023-08-18 11:07 dpdklab
2023-08-18 11:08 dpdklab
2023-08-18 11:08 dpdklab
2023-08-18 11:12 dpdklab
2023-08-18 11:15 dpdklab
2023-08-18 11:16 dpdklab
2023-08-18 11:18 dpdklab
2023-08-18 11:20 dpdklab
2023-08-18 11:20 dpdklab
2023-08-18 11:21 dpdklab
2023-08-18 11:21 dpdklab
2023-08-18 11:30 dpdklab
2023-08-18 11:33 dpdklab
2023-08-18 11:35 dpdklab
2023-08-18 11:36 dpdklab
2023-08-18 11:36 dpdklab
2023-08-18 11:36 dpdklab
2023-08-18 11:38 dpdklab
2023-08-18 11:39 dpdklab
2023-08-18 11:42 dpdklab
2023-08-18 11:47 dpdklab
2023-08-18 11:48 dpdklab
2023-08-18 11:48 dpdklab
2023-08-18 11:49 dpdklab
2023-08-18 11:50 dpdklab
2023-08-18 11:51 dpdklab
2023-08-18 11:51 dpdklab
2023-08-18 11:54 dpdklab
2023-08-18 11:55 dpdklab
2023-08-18 11:59 dpdklab
2023-08-18 12:02 dpdklab
2023-08-18 12:02 dpdklab
2023-08-18 12:19 dpdklab
2023-08-18 12:35 dpdklab
2023-08-18 12:54 dpdklab
2023-08-18 12:55 dpdklab
2023-08-18 23:44 dpdklab
2023-08-18 23:55 dpdklab
2023-08-18 23:59 dpdklab
2023-08-19 0:16 dpdklab
2023-08-19 0:20 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=202308180349.37I3naYn3432748@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).