From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw141142-141152 [PATCH v2 11/11] doc: update nfp document
Date: Fri, 14 Jun 2024 14:43:34 +0800 [thread overview]
Message-ID: <202406140643.45E6hYtI2685418@localhost.localdomain> (raw)
In-Reply-To: <20240614070120.2663160-12-chaoyong.he@corigine.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/141152
_Compilation OK_
Submitter: Chaoyong He <chaoyong.he@corigine.com>
Date: Fri, 14 Jun 2024 15:01:10 +0800
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: fbba6db3640f9f623c29c452e1a6b057073e81d2
141142-141152 --> 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-06-14 7:12 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240614070120.2663160-12-chaoyong.he@corigine.com>
2024-06-14 6:43 ` qemudev [this message]
2024-06-14 6:48 ` qemudev
2024-06-14 7:04 ` |SUCCESS| pw141152 " checkpatch
2024-06-14 8:06 ` |FAILURE| " 0-day Robot
2024-06-14 9:19 ` |SUCCESS| pw141142-141152 [PATCH] [v2,11/11] doc: update nfp documen dpdklab
2024-06-14 9:50 ` dpdklab
2024-06-14 10:05 ` dpdklab
2024-06-14 10:09 ` dpdklab
2024-06-14 10:12 ` dpdklab
2024-06-14 10:13 ` dpdklab
2024-06-14 10:14 ` dpdklab
2024-06-14 10:15 ` dpdklab
2024-06-14 10:17 ` dpdklab
2024-06-14 10:21 ` dpdklab
2024-06-14 10:26 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:27 ` dpdklab
2024-06-14 10:28 ` dpdklab
2024-06-14 10:35 ` dpdklab
2024-06-14 10:35 ` dpdklab
2024-06-14 10:36 ` dpdklab
2024-06-14 10:37 ` dpdklab
2024-06-14 10:38 ` dpdklab
2024-06-14 10:39 ` dpdklab
2024-06-14 10:41 ` dpdklab
2024-06-14 10:56 ` dpdklab
2024-06-14 11:04 ` dpdklab
2024-06-14 11:18 ` dpdklab
2024-06-14 11:35 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:36 ` dpdklab
2024-06-14 11:37 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:38 ` dpdklab
2024-06-14 11:39 ` dpdklab
2024-06-14 11:39 ` dpdklab
2024-06-14 11:40 ` dpdklab
2024-06-14 11:41 ` dpdklab
2024-06-14 11:48 ` dpdklab
2024-06-14 11:48 ` dpdklab
2024-06-14 11:49 ` dpdklab
2024-06-14 11:52 ` dpdklab
2024-06-14 11:55 ` dpdklab
2024-06-14 11:56 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:57 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 11:59 ` dpdklab
2024-06-14 12:00 ` dpdklab
2024-06-14 12:00 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:01 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:02 ` dpdklab
2024-06-14 12:03 ` dpdklab
2024-06-14 12:06 ` dpdklab
2024-06-14 12:07 ` dpdklab
2024-06-14 12:07 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:09 ` dpdklab
2024-06-14 12:10 ` dpdklab
2024-06-14 12:27 ` dpdklab
2024-06-14 12:27 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:28 ` dpdklab
2024-06-14 12:29 ` dpdklab
2024-06-14 12:37 ` dpdklab
2024-06-14 12:40 ` dpdklab
2024-06-14 12:46 ` dpdklab
2024-06-14 12:48 ` dpdklab
2024-06-14 12:48 ` dpdklab
2024-06-14 12:52 ` dpdklab
2024-06-14 12:55 ` dpdklab
2024-06-14 12:56 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:57 ` dpdklab
2024-06-14 12:58 ` dpdklab
2024-06-14 13:24 ` dpdklab
2024-06-14 13:28 ` dpdklab
2024-06-14 13:29 ` dpdklab
2024-06-14 13:33 ` dpdklab
2024-06-14 14:07 ` dpdklab
2024-06-14 14:13 ` dpdklab
2024-06-14 14:14 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:17 ` dpdklab
2024-06-14 14:34 ` 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=202406140643.45E6hYtI2685418@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).