From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw124872 [PATCH v2] net/cpfl: fix a compiler issue about virtchnl opcode
Date: Thu, 9 Mar 2023 10:13:45 +0800 [thread overview]
Message-ID: <202303090213.3292Djnv1436693@localhost.localdomain> (raw)
In-Reply-To: <20230309103811.277553-1-mingxia.liu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/124872
_Compilation OK_
Submitter: Mingxia Liu <mingxia.liu@intel.com>
Date: Thu, 9 Mar 2023 10:38:11 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2f167601c68cedd3e0e3bd16169da92fc7948035
124872 --> 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-09 2:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230309103811.277553-1-mingxia.liu@intel.com>
2023-03-09 2:13 ` qemudev [this message]
2023-03-09 2:17 ` qemudev
2023-03-09 2:23 ` checkpatch
2023-03-09 4:39 ` 0-day Robot
2023-03-10 4:05 |SUCCESS| pw124872 [PATCH] [v2] " dpdklab
2023-03-10 4:32 dpdklab
2023-03-10 4:43 dpdklab
2023-03-10 4:52 dpdklab
2023-03-10 5:08 dpdklab
2023-03-10 5:13 dpdklab
2023-03-10 5:17 dpdklab
2023-03-10 5:18 dpdklab
2023-03-10 5:27 dpdklab
2023-03-10 5:33 dpdklab
2023-03-10 5:40 dpdklab
2023-03-10 5:53 dpdklab
2023-03-10 6:07 dpdklab
2023-03-10 6:20 dpdklab
2023-03-10 17:44 dpdklab
2023-03-11 6:16 dpdklab
2023-03-11 6:16 dpdklab
2023-03-11 6:30 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=202303090213.3292Djnv1436693@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).