From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139829-139855 [PATCH v2 27/27] net/ixgbe/base: add various miscellaneous features
Date: Fri, 3 May 2024 21:39:46 +0800 [thread overview]
Message-ID: <202405031339.443DdkJB906777@localhost.localdomain> (raw)
In-Reply-To: <93795571c98db29f975ee12675246b5169c7082e.1714744629.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139855
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Fri, 3 May 2024 14:57:32 +0100
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 2ac57ed414af92f0c30a799e1824fd47f86a94b0
139829-139855 --> 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:[~2024-05-03 14:07 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <93795571c98db29f975ee12675246b5169c7082e.1714744629.git.anatoly.burakov@intel.com>
2024-05-03 13:39 ` qemudev [this message]
2024-05-03 13:44 ` qemudev
2024-05-03 14:03 ` |WARNING| pw139855 " checkpatch
2024-05-03 15:00 ` |SUCCESS| pw139829-139855 [PATCH] [v2,27/27] net/ixgbe/base: add var dpdklab
2024-05-03 15:01 ` dpdklab
2024-05-03 15:01 ` dpdklab
2024-05-03 15:01 ` dpdklab
2024-05-03 15:02 ` dpdklab
2024-05-03 15:02 ` dpdklab
2024-05-03 15:02 ` dpdklab
2024-05-03 15:03 ` dpdklab
2024-05-03 15:03 ` dpdklab
2024-05-03 15:03 ` dpdklab
2024-05-03 15:03 ` dpdklab
2024-05-03 15:03 ` |SUCCESS| pw139855 [PATCH v2 27/27] net/ixgbe/base: add various miscellaneous features 0-day Robot
2024-05-03 15:03 ` |SUCCESS| pw139829-139855 [PATCH] [v2,27/27] net/ixgbe/base: add var dpdklab
2024-05-03 15:04 ` dpdklab
2024-05-03 15:04 ` dpdklab
2024-05-03 15:05 ` dpdklab
2024-05-03 15:05 ` dpdklab
2024-05-03 15:05 ` dpdklab
2024-05-03 15:05 ` dpdklab
2024-05-03 15:06 ` dpdklab
2024-05-03 15:06 ` dpdklab
2024-05-03 15:06 ` dpdklab
2024-05-03 15:07 ` dpdklab
2024-05-03 15:07 ` dpdklab
2024-05-03 15:07 ` dpdklab
2024-05-03 15:07 ` dpdklab
2024-05-03 15:08 ` dpdklab
2024-05-03 15:08 ` dpdklab
2024-05-03 15:08 ` dpdklab
2024-05-03 15:08 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:09 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:10 ` dpdklab
2024-05-03 15:11 ` dpdklab
2024-05-03 15:12 ` dpdklab
2024-05-03 15:14 ` dpdklab
2024-05-03 15:14 ` dpdklab
2024-05-03 15:15 ` dpdklab
2024-05-03 15:15 ` dpdklab
2024-05-03 15:16 ` dpdklab
2024-05-03 15:17 ` dpdklab
2024-05-03 15:17 ` dpdklab
2024-05-03 15:17 ` dpdklab
2024-05-03 15:19 ` dpdklab
2024-05-03 15:21 ` dpdklab
2024-05-03 15:21 ` dpdklab
2024-05-03 15:22 ` dpdklab
2024-05-03 15:24 ` dpdklab
2024-05-03 15:25 ` dpdklab
2024-05-03 15:25 ` dpdklab
2024-05-03 15:26 ` dpdklab
2024-05-03 15:27 ` dpdklab
2024-05-03 15:28 ` dpdklab
2024-05-03 15:30 ` dpdklab
2024-05-03 15:34 ` dpdklab
2024-05-03 15:34 ` dpdklab
2024-05-03 15:36 ` dpdklab
2024-05-03 15:36 ` dpdklab
2024-05-03 15:38 ` dpdklab
2024-05-03 15:42 ` dpdklab
2024-05-03 15:43 ` dpdklab
2024-05-03 15:43 ` dpdklab
2024-05-03 15:46 ` dpdklab
2024-05-03 15:50 ` dpdklab
2024-05-03 15:50 ` dpdklab
2024-05-03 15:57 ` dpdklab
2024-05-03 16:03 ` dpdklab
2024-05-03 16:06 ` dpdklab
2024-05-03 16:37 ` dpdklab
2024-05-03 17:17 ` dpdklab
2024-05-03 17:25 ` dpdklab
2024-05-03 17:31 ` dpdklab
2024-05-03 20:23 ` dpdklab
2024-05-05 7:48 ` dpdklab
2024-05-05 7:55 ` dpdklab
2024-05-05 7:59 ` dpdklab
2024-05-05 8:04 ` dpdklab
2024-05-05 8:08 ` dpdklab
2024-05-06 11:46 ` 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=202405031339.443DdkJB906777@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).