From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139689-139698 [PATCH 10/10] doc: update nfp document
Date: Fri, 26 Apr 2024 15:36:57 +0800 [thread overview]
Message-ID: <202404260736.43Q7av412210608@localhost.localdomain> (raw)
In-Reply-To: <20240426074831.1729792-11-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139698
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 26 Apr 2024 15:48:22 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 8841786ab4aa72d205f97528af8708a13a851f4f
139689-139698 --> 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-04-26 8:04 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240426074831.1729792-11-chaoyong.he@corigine.com>
2024-04-26 7:36 ` qemudev [this message]
2024-04-26 7:41 ` qemudev
2024-04-26 8:52 ` |SUCCESS| pw139689-139698 [PATCH] [10/10] " dpdklab
2024-04-26 8:53 ` dpdklab
2024-04-26 8:55 ` dpdklab
2024-04-26 8:58 ` dpdklab
2024-04-26 8:58 ` dpdklab
2024-04-26 8:58 ` dpdklab
2024-04-26 8:59 ` dpdklab
2024-04-26 9:01 ` dpdklab
2024-04-26 9:02 ` dpdklab
2024-04-26 9:02 ` dpdklab
2024-04-26 9:02 ` dpdklab
2024-04-26 9:03 ` dpdklab
2024-04-26 9:03 ` |FAILURE| " dpdklab
2024-04-26 9:03 ` |SUCCESS| " dpdklab
2024-04-26 9:03 ` |FAILURE| " dpdklab
2024-04-26 9:04 ` |SUCCESS| " dpdklab
2024-04-26 9:04 ` dpdklab
2024-04-26 9:04 ` dpdklab
2024-04-26 9:04 ` |FAILURE| " dpdklab
2024-04-26 9:04 ` |SUCCESS| " dpdklab
2024-04-26 9:04 ` dpdklab
2024-04-26 9:05 ` dpdklab
2024-04-26 9:05 ` |FAILURE| " dpdklab
2024-04-26 9:05 ` |SUCCESS| " dpdklab
2024-04-26 9:06 ` dpdklab
2024-04-26 9:06 ` dpdklab
2024-04-26 9:06 ` |FAILURE| " dpdklab
2024-04-26 9:06 ` |SUCCESS| " dpdklab
2024-04-26 9:06 ` dpdklab
2024-04-26 9:07 ` |FAILURE| " dpdklab
2024-04-26 9:07 ` |SUCCESS| " dpdklab
2024-04-26 9:08 ` dpdklab
2024-04-26 9:08 ` dpdklab
2024-04-26 9:08 ` dpdklab
2024-04-26 9:09 ` dpdklab
2024-04-26 9:09 ` dpdklab
2024-04-26 9:10 ` dpdklab
2024-04-26 9:10 ` dpdklab
2024-04-26 9:10 ` dpdklab
2024-04-26 9:11 ` |FAILURE| " dpdklab
2024-04-26 9:11 ` |SUCCESS| " dpdklab
2024-04-26 9:11 ` dpdklab
2024-04-26 9:12 ` dpdklab
2024-04-26 9:12 ` |FAILURE| " dpdklab
2024-04-26 9:12 ` |SUCCESS| " dpdklab
2024-04-26 9:16 ` dpdklab
2024-04-26 9:17 ` dpdklab
2024-04-26 9:19 ` dpdklab
2024-04-26 9:20 ` |FAILURE| " dpdklab
2024-04-26 9:20 ` |SUCCESS| " dpdklab
2024-04-26 9:27 ` dpdklab
2024-04-26 9:28 ` dpdklab
2024-04-26 9:28 ` dpdklab
2024-04-26 9:29 ` dpdklab
2024-04-26 9:29 ` dpdklab
2024-04-26 9:29 ` dpdklab
2024-04-26 9:30 ` dpdklab
2024-04-26 9:32 ` dpdklab
2024-04-26 9:32 ` dpdklab
2024-04-26 9:32 ` dpdklab
2024-04-26 9:33 ` dpdklab
2024-04-26 9:35 ` dpdklab
2024-04-26 9:35 ` |FAILURE| " dpdklab
2024-04-26 9:36 ` |SUCCESS| " dpdklab
2024-04-26 9:39 ` dpdklab
2024-04-26 9:40 ` dpdklab
2024-04-26 9:48 ` dpdklab
2024-04-26 9:49 ` dpdklab
2024-04-26 10:00 ` dpdklab
2024-04-26 10:01 ` dpdklab
2024-04-26 10:12 ` dpdklab
2024-04-26 10:48 ` dpdklab
2024-04-26 22:27 ` dpdklab
2024-04-26 22:45 ` dpdklab
2024-04-26 22:48 ` dpdklab
2024-04-26 23:25 ` dpdklab
2024-04-26 23:25 ` dpdklab
2024-04-26 23:25 ` dpdklab
2024-04-26 23:27 ` dpdklab
2024-04-26 23:29 ` dpdklab
2024-04-26 23:32 ` dpdklab
2024-04-26 23:32 ` dpdklab
2024-04-26 23:32 ` dpdklab
2024-04-26 23:35 ` dpdklab
2024-04-26 23:36 ` dpdklab
2024-04-26 23:38 ` dpdklab
2024-04-26 23:40 ` dpdklab
2024-04-26 23:44 ` dpdklab
2024-04-26 23:46 ` dpdklab
2024-05-03 12:31 ` |SUCCESS| pw139698 [PATCH 10/10] " checkpatch
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=202404260736.43Q7av412210608@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).