From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140137 [PATCH v1] net/cpfl: check if DPDK is running on host IMC ACC
Date: Thu, 16 May 2024 15:52:17 +0800 [thread overview]
Message-ID: <202405160752.44G7qHS94140423@localhost.localdomain> (raw)
In-Reply-To: <20240516081243.576723-1-shaiqwani@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140137
_Compilation OK_
Submitter: Shaiq Wani <shaiqwani@intel.com>
Date: Thu, 16 May 2024 08:12:43 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
140137 --> 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-16 8:20 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240516081243.576723-1-shaiqwani@intel.com>
2024-05-16 7:52 ` qemudev [this message]
2024-05-16 7:56 ` qemudev
2024-05-16 8:17 ` checkpatch
2024-05-16 9:04 ` 0-day Robot
2024-05-16 9:27 ` |SUCCESS| pw140137 [PATCH] [v1] net/cpfl: check if DPDK is running o dpdklab
2024-05-16 9:28 ` dpdklab
2024-05-16 9:29 ` dpdklab
2024-05-16 9:29 ` dpdklab
2024-05-16 9:33 ` dpdklab
2024-05-16 9:46 ` dpdklab
2024-05-16 9:46 ` dpdklab
2024-05-16 9:48 ` dpdklab
2024-05-16 9:49 ` dpdklab
2024-05-16 9:50 ` dpdklab
2024-05-16 9:50 ` dpdklab
2024-05-16 9:50 ` dpdklab
2024-05-16 9:52 ` dpdklab
2024-05-16 9:52 ` dpdklab
2024-05-16 9:53 ` dpdklab
2024-05-16 9:53 ` dpdklab
2024-05-16 9:53 ` dpdklab
2024-05-16 9:54 ` dpdklab
2024-05-16 9:54 ` dpdklab
2024-05-16 9:54 ` dpdklab
2024-05-16 9:54 ` dpdklab
2024-05-16 9:55 ` dpdklab
2024-05-16 9:55 ` dpdklab
2024-05-16 9:55 ` dpdklab
2024-05-16 9:56 ` dpdklab
2024-05-16 9:56 ` dpdklab
2024-05-16 9:56 ` dpdklab
2024-05-16 9:56 ` dpdklab
2024-05-16 9:57 ` dpdklab
2024-05-16 9:57 ` dpdklab
2024-05-16 9:57 ` dpdklab
2024-05-16 9:57 ` dpdklab
2024-05-16 9:58 ` dpdklab
2024-05-16 9:58 ` dpdklab
2024-05-16 9:58 ` dpdklab
2024-05-16 9:59 ` dpdklab
2024-05-16 9:59 ` dpdklab
2024-05-16 9:59 ` dpdklab
2024-05-16 9:59 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:00 ` dpdklab
2024-05-16 10:01 ` dpdklab
2024-05-16 10:01 ` dpdklab
2024-05-16 10:03 ` dpdklab
2024-05-16 10:03 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:04 ` dpdklab
2024-05-16 10:06 ` dpdklab
2024-05-16 10:07 ` dpdklab
2024-05-16 10:09 ` dpdklab
2024-05-16 10:09 ` dpdklab
2024-05-16 10:10 ` dpdklab
2024-05-16 10:10 ` dpdklab
2024-05-16 10:11 ` dpdklab
2024-05-16 10:12 ` dpdklab
2024-05-16 10:13 ` dpdklab
2024-05-16 10:13 ` dpdklab
2024-05-16 10:14 ` dpdklab
2024-05-16 10:14 ` dpdklab
2024-05-16 10:15 ` dpdklab
2024-05-16 10:17 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:18 ` dpdklab
2024-05-16 10:21 ` dpdklab
2024-05-16 10:22 ` dpdklab
2024-05-16 10:22 ` dpdklab
2024-05-16 10:23 ` dpdklab
2024-05-16 10:25 ` dpdklab
2024-05-16 10:25 ` dpdklab
2024-05-16 10:35 ` dpdklab
2024-05-16 10:41 ` dpdklab
2024-05-16 10:52 ` dpdklab
2024-05-16 11:02 ` dpdklab
2024-05-16 11:11 ` dpdklab
2024-05-16 12:26 ` 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=202405160752.44G7qHS94140423@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).