From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw142807 [PATCH v1] net/i40e: updated 24.07 recommended matching list
Date: Thu, 1 Aug 2024 16:30:12 +0800 [thread overview]
Message-ID: <202408010830.4718UCec119331@localhost.localdomain> (raw)
In-Reply-To: <20240801081902.750080-1-hailinx.xu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/142807
_Compilation OK_
Submitter: hailinx <hailinx.xu@intel.com>
Date: Thu, 1 Aug 2024 16:19:02 +0800
DPDK git baseline: Repo:dpdk-next-net-intel
Branch: main
CommitID: 3b017bdc4c25e2cd6733a9363e9c566b95834cc4
142807 --> 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-08-01 8:59 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240801081902.750080-1-hailinx.xu@intel.com>
2024-08-01 8:30 ` qemudev [this message]
2024-08-01 8:34 ` qemudev
2024-08-01 8:58 ` |WARNING| " checkpatch
2024-08-01 9:42 ` |SUCCESS| " 0-day Robot
2024-08-01 18:11 ` |PENDING| pw142807 [PATCH] [v1] net/i40e: updated 24.07 recommended dpdklab
2024-08-01 18:11 ` dpdklab
2024-08-01 18:12 ` dpdklab
2024-08-01 18:12 ` dpdklab
2024-08-01 18:13 ` dpdklab
2024-08-01 18:14 ` |SUCCESS| " dpdklab
2024-08-01 18:15 ` |PENDING| " dpdklab
2024-08-01 18:16 ` dpdklab
2024-08-01 18:17 ` dpdklab
2024-08-01 18:20 ` dpdklab
2024-08-01 18:20 ` dpdklab
2024-08-01 18:21 ` dpdklab
2024-08-01 18:21 ` dpdklab
2024-08-01 18:22 ` dpdklab
2024-08-01 18:25 ` |SUCCESS| " dpdklab
2024-08-01 18:26 ` |PENDING| " dpdklab
2024-08-01 18:27 ` dpdklab
2024-08-01 18:28 ` dpdklab
2024-08-01 18:32 ` dpdklab
2024-08-01 18:36 ` dpdklab
2024-08-01 18:36 ` dpdklab
2024-08-01 18:39 ` dpdklab
2024-08-01 18:41 ` dpdklab
2024-08-01 18:42 ` dpdklab
2024-08-01 18:43 ` dpdklab
2024-08-01 18:44 ` dpdklab
2024-08-01 18:46 ` dpdklab
2024-08-01 18:46 ` dpdklab
2024-08-01 18:47 ` dpdklab
2024-08-01 18:50 ` |SUCCESS| " dpdklab
2024-08-01 18:50 ` |PENDING| " dpdklab
2024-08-01 18:50 ` |SUCCESS| " dpdklab
2024-08-01 18:51 ` |PENDING| " dpdklab
2024-08-01 18:52 ` dpdklab
2024-08-01 18:52 ` dpdklab
2024-08-01 18:56 ` dpdklab
2024-08-01 18:58 ` |SUCCESS| " dpdklab
2024-08-01 20:14 ` |PENDING| " dpdklab
2024-08-01 20:17 ` dpdklab
2024-08-01 20:20 ` dpdklab
2024-08-01 20:24 ` dpdklab
2024-08-01 20:26 ` dpdklab
2024-08-01 20:28 ` dpdklab
2024-08-01 20:33 ` dpdklab
2024-08-01 20:40 ` dpdklab
2024-08-01 20:48 ` dpdklab
2024-08-01 20:55 ` dpdklab
2024-08-01 21:03 ` dpdklab
2024-08-01 21:11 ` dpdklab
2024-08-01 21:17 ` dpdklab
2024-08-01 21:18 ` dpdklab
2024-08-01 21:20 ` dpdklab
2024-08-01 21:25 ` dpdklab
2024-08-01 21:27 ` dpdklab
2024-08-01 21:31 ` dpdklab
2024-08-01 21:33 ` dpdklab
2024-08-01 21:34 ` dpdklab
2024-08-01 21:35 ` dpdklab
2024-08-01 21:39 ` dpdklab
2024-08-01 21:42 ` dpdklab
2024-08-01 21:44 ` dpdklab
2024-08-01 21:44 ` dpdklab
2024-08-01 21:45 ` dpdklab
2024-08-01 21:46 ` dpdklab
2024-08-01 21:46 ` dpdklab
2024-08-01 21:47 ` dpdklab
2024-08-01 21:47 ` dpdklab
2024-08-01 21:52 ` dpdklab
2024-08-01 21:55 ` dpdklab
2024-08-01 21:58 ` dpdklab
2024-08-01 22:09 ` dpdklab
2024-08-01 22:12 ` |SUCCESS| " dpdklab
2024-08-02 0:22 ` dpdklab
2024-08-02 21:29 ` dpdklab
2024-08-02 21:45 ` |PENDING| " dpdklab
2024-08-02 21:53 ` dpdklab
2024-08-02 21:58 ` |SUCCESS| " dpdklab
2024-08-02 22:06 ` dpdklab
2024-08-02 22:07 ` dpdklab
2024-08-02 22:16 ` dpdklab
2024-08-02 22:17 ` dpdklab
2024-08-02 22:18 ` dpdklab
2024-08-02 22:21 ` dpdklab
2024-08-02 22:25 ` dpdklab
2024-08-02 22:29 ` dpdklab
2024-08-02 22:49 ` dpdklab
2024-08-02 22:50 ` dpdklab
2024-08-03 0:09 ` 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=202408010830.4718UCec119331@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).