From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124286 [PATCH v2] app/testpmd: fix flex item compilation error
Date: Tue, 21 Feb 2023 17:50:43 +0800 [thread overview]
Message-ID: <202302210950.31L9ohTu818590@localhost.localdomain> (raw)
In-Reply-To: <20230221100201.361765-1-rongweil@nvidia.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124286
_Compilation OK_
Submitter: Rongwei Liu <rongweil@nvidia.com>
Date: Tue, 21 Feb 2023 12:02:01 +0200
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 74ef0e382c258b031e752c9ef5c6872a4da1c28d
124286 --> 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-02-21 10:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230221100201.361765-1-rongweil@nvidia.com>
2023-02-21 9:50 ` qemudev [this message]
2023-02-21 9:54 ` qemudev
2023-02-21 10:03 ` |WARNING| " checkpatch
2023-02-21 12:19 ` |SUCCESS| " 0-day Robot
2023-02-21 19:00 |SUCCESS| pw124286 [PATCH] [v2] " dpdklab
2023-02-21 19:34 dpdklab
2023-02-21 19:39 dpdklab
2023-02-21 19:46 dpdklab
2023-02-21 19:50 dpdklab
2023-02-21 20:03 dpdklab
2023-02-21 20:10 dpdklab
2023-02-21 20:23 dpdklab
2023-02-21 20:43 dpdklab
2023-02-22 2:14 dpdklab
2023-02-22 2:18 dpdklab
2023-02-22 2:20 dpdklab
2023-02-22 2:27 dpdklab
2023-02-22 2:27 dpdklab
2023-02-22 2:33 dpdklab
2023-02-22 2:41 dpdklab
2023-02-22 2:47 dpdklab
2023-02-22 2:49 dpdklab
2023-02-22 2:52 dpdklab
2023-02-22 2:54 dpdklab
2023-02-22 2:56 dpdklab
2023-02-22 2:56 dpdklab
2023-02-22 3:39 dpdklab
2023-02-23 16:12 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=202302210950.31L9ohTu818590@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).