From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw125890 [PATCH v7] net/ice: fix ice dcf control thread crash
Date: Tue, 11 Apr 2023 10:02:44 +0800 [thread overview]
Message-ID: <202304110202.33B22iWG2681309@localhost.localdomain> (raw)
In-Reply-To: <20230411020855.314971-1-mingjinx.ye@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/125890
_Compilation OK_
Submitter: Mingjin Ye <mingjinx.ye@intel.com>
Date: Tue, 11 Apr 2023 02:08:55 +0000
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 3bc3d9f9f3df2e22c3958d1a3dac68ce2d708b33
125890 --> 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-04-11 2:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230411020855.314971-1-mingjinx.ye@intel.com>
2023-04-11 2:02 ` qemudev [this message]
2023-04-11 2:06 ` qemudev
2023-04-11 2:14 ` checkpatch
2023-04-11 2:58 ` 0-day Robot
2023-04-11 2:39 |SUCCESS| pw125890 [PATCH] [v7] " dpdklab
2023-04-11 2:45 dpdklab
2023-04-11 2:45 dpdklab
2023-04-11 2:50 dpdklab
2023-04-11 2:53 dpdklab
2023-04-11 2:53 dpdklab
2023-04-11 2:57 dpdklab
2023-04-11 2:57 dpdklab
2023-04-11 3:06 dpdklab
2023-04-11 3:09 dpdklab
2023-04-11 3:11 dpdklab
2023-04-11 3:13 dpdklab
2023-04-11 3:13 dpdklab
2023-04-11 3:14 dpdklab
2023-04-11 3:15 dpdklab
2023-04-11 3:15 dpdklab
2023-04-11 3:17 dpdklab
2023-04-11 3:23 dpdklab
2023-04-11 3:23 dpdklab
2023-04-11 3:33 dpdklab
2023-04-11 3:39 dpdklab
2023-04-11 3:42 dpdklab
2023-04-11 3:42 dpdklab
2023-04-11 3:48 dpdklab
2023-04-11 4:12 dpdklab
2023-04-11 13:46 dpdklab
2023-04-11 13:50 dpdklab
2023-04-11 13:55 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=202304110202.33B22iWG2681309@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).