From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125254 [PATCH] config/arm: enable rcpc feature on neoverse n1
Date: Mon, 20 Mar 2023 11:16:30 +0800 [thread overview]
Message-ID: <202303200316.32K3GUTK2010036@localhost.localdomain> (raw)
In-Reply-To: <20230320032655.2119718-1-joyce.kong@arm.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125254
_Compilation OK_
Submitter: Joyce Kong <joyce.kong@arm.com>
Date: Mon, 20 Mar 2023 03:26:55 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: f1d0993e034e39968a2c80a8561b46c260c27487
125254 --> 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-03-20 3:30 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230320032655.2119718-1-joyce.kong@arm.com>
2023-03-20 3:16 ` qemudev [this message]
2023-03-20 3:20 ` qemudev
2023-03-20 3:28 ` checkpatch
2023-03-20 5:39 ` 0-day Robot
2023-03-20 4:02 dpdklab
2023-03-20 4:07 dpdklab
2023-03-20 4:13 dpdklab
2023-03-20 4:15 dpdklab
2023-03-20 4:16 dpdklab
2023-03-20 4:17 dpdklab
2023-03-20 4:18 dpdklab
2023-03-20 4:24 dpdklab
2023-03-20 4:26 dpdklab
2023-03-20 4:28 dpdklab
2023-03-20 4:29 dpdklab
2023-03-20 4:32 dpdklab
2023-03-20 4:34 dpdklab
2023-03-20 4:38 dpdklab
2023-03-20 4:40 dpdklab
2023-03-20 4:43 dpdklab
2023-03-20 4:46 dpdklab
2023-03-20 4:47 dpdklab
2023-03-20 4:48 dpdklab
2023-03-20 4:51 dpdklab
2023-03-20 4:58 dpdklab
2023-03-20 5:21 dpdklab
2023-03-20 5:32 dpdklab
2023-03-20 6:02 dpdklab
2023-03-20 6:13 dpdklab
2023-03-20 7:51 dpdklab
2023-03-20 17:19 dpdklab
2023-03-20 18:28 dpdklab
2023-03-20 19:31 dpdklab
2023-03-22 11:25 dpdklab
2023-03-22 11:25 dpdklab
2023-03-22 12:16 dpdklab
2023-03-22 13:21 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=202303200316.32K3GUTK2010036@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).