From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw135173 [PATCH v2] net/ice: fix link update
Date: Thu, 14 Dec 2023 08:01:48 +0800 [thread overview]
Message-ID: <202312140001.3BE01mGW309558@localhost.localdomain> (raw)
In-Reply-To: <20231214084054.2593194-1-qi.z.zhang@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/135173
_Compilation OK_
Submitter: Qi Zhang <qi.z.zhang@intel.com>
Date: Thu, 14 Dec 2023 03:40:54 -0500
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: e5dc404d33ac1c6cea5c62a88489746c5cb5e35e
135173 --> 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-12-14 0:22 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231214084054.2593194-1-qi.z.zhang@intel.com>
2023-12-14 0:01 ` qemudev [this message]
2023-12-14 0:06 ` qemudev
2023-12-14 0:21 ` |WARNING| " checkpatch
2023-12-14 1:24 ` |SUCCESS| " 0-day Robot
2023-12-14 1:06 |SUCCESS| pw135173 [PATCH] [v2] " dpdklab
2023-12-14 1:07 dpdklab
2023-12-14 1:07 dpdklab
2023-12-14 1:08 dpdklab
2023-12-14 1:08 dpdklab
2023-12-14 1:08 dpdklab
2023-12-14 1:09 dpdklab
2023-12-14 1:09 dpdklab
2023-12-14 1:09 dpdklab
2023-12-14 1:09 dpdklab
2023-12-14 1:10 dpdklab
2023-12-14 1:10 dpdklab
2023-12-14 1:10 dpdklab
2023-12-14 1:11 dpdklab
2023-12-14 1:11 dpdklab
2023-12-14 1:11 dpdklab
2023-12-14 1:12 dpdklab
2023-12-14 1:12 dpdklab
2023-12-14 1:12 dpdklab
2023-12-14 1:12 dpdklab
2023-12-14 1:13 dpdklab
2023-12-14 1:13 dpdklab
2023-12-14 1:13 dpdklab
2023-12-14 1:13 dpdklab
2023-12-14 1:14 dpdklab
2023-12-14 1:14 dpdklab
2023-12-14 1:14 dpdklab
2023-12-14 1:15 dpdklab
2023-12-14 1:16 dpdklab
2023-12-14 1:18 dpdklab
2023-12-14 1:18 dpdklab
2023-12-14 1:18 dpdklab
2023-12-14 1:19 dpdklab
2023-12-14 1:19 dpdklab
2023-12-14 1:20 dpdklab
2023-12-14 1:20 dpdklab
2023-12-14 1:20 dpdklab
2023-12-14 1:20 dpdklab
2023-12-14 1:20 dpdklab
2023-12-14 1:21 dpdklab
2023-12-14 1:21 dpdklab
2023-12-14 1:21 dpdklab
2023-12-14 1:22 dpdklab
2023-12-14 1:23 dpdklab
2023-12-14 1:23 dpdklab
2023-12-14 1:23 dpdklab
2023-12-14 1:24 dpdklab
2023-12-14 1:25 dpdklab
2023-12-14 1:25 dpdklab
2023-12-14 1:26 dpdklab
2023-12-14 1:26 dpdklab
2023-12-14 1:27 dpdklab
2023-12-14 1:27 dpdklab
2023-12-14 1:30 dpdklab
2023-12-14 1:31 dpdklab
2023-12-14 1:31 dpdklab
2023-12-14 1:33 dpdklab
2023-12-14 1:35 dpdklab
2023-12-14 1:35 dpdklab
2023-12-14 1:35 dpdklab
2023-12-14 1:37 dpdklab
2023-12-14 1:38 dpdklab
2023-12-14 1:39 dpdklab
2023-12-14 1:39 dpdklab
2023-12-14 1:47 dpdklab
2023-12-14 1:48 dpdklab
2023-12-14 2:02 dpdklab
2023-12-14 3:56 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=202312140001.3BE01mGW309558@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).