From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140207-140217 [PATCH v14 11/11] net/tap: update documentation
Date: Wed, 22 May 2024 00:55:41 +0800 [thread overview]
Message-ID: <202405211655.44LGtf5O595909@localhost.localdomain> (raw)
In-Reply-To: <20240521170746.119330-12-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140217
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 21 May 2024 10:06:01 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6f80df8cb0f889203d7cd27766abcc6ebc720e33
140207-140217 --> 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-21 17:24 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240521170746.119330-12-stephen@networkplumber.org>
2024-05-21 16:55 ` qemudev [this message]
2024-05-21 17:00 ` qemudev
2024-05-21 17:09 ` |SUCCESS| pw140217 " checkpatch
2024-05-21 17:51 ` |SUCCESS| pw140207-140217 [PATCH] [v14,11/11] net/tap: update docume dpdklab
2024-05-21 17:51 ` dpdklab
2024-05-21 17:51 ` dpdklab
2024-05-21 17:52 ` dpdklab
2024-05-21 17:53 ` dpdklab
2024-05-21 18:00 ` dpdklab
2024-05-21 18:00 ` dpdklab
2024-05-21 18:01 ` dpdklab
2024-05-21 18:01 ` dpdklab
2024-05-21 18:02 ` dpdklab
2024-05-21 18:03 ` dpdklab
2024-05-21 18:04 ` dpdklab
2024-05-21 18:04 ` dpdklab
2024-05-21 18:05 ` dpdklab
2024-05-21 18:05 ` dpdklab
2024-05-21 18:06 ` dpdklab
2024-05-21 18:06 ` dpdklab
2024-05-21 18:07 ` dpdklab
2024-05-21 18:07 ` |FAILURE| pw140217 [PATCH v14 11/11] net/tap: update documentation 0-day Robot
2024-05-21 18:07 ` |SUCCESS| pw140207-140217 [PATCH] [v14,11/11] net/tap: update docume dpdklab
2024-05-21 18:08 ` dpdklab
2024-05-21 18:08 ` dpdklab
2024-05-21 18:13 ` dpdklab
2024-05-21 18:14 ` dpdklab
2024-05-21 18:14 ` dpdklab
2024-05-21 18:14 ` dpdklab
2024-05-21 18:14 ` dpdklab
2024-05-21 18:15 ` dpdklab
2024-05-21 18:15 ` dpdklab
2024-05-21 18:15 ` dpdklab
2024-05-21 18:16 ` dpdklab
2024-05-21 18:16 ` dpdklab
2024-05-21 18:16 ` dpdklab
2024-05-21 18:16 ` dpdklab
2024-05-21 18:16 ` dpdklab
2024-05-21 18:17 ` dpdklab
2024-05-21 18:17 ` dpdklab
2024-05-21 18:17 ` dpdklab
2024-05-21 18:17 ` dpdklab
2024-05-21 18:18 ` dpdklab
2024-05-21 18:18 ` dpdklab
2024-05-21 18:18 ` dpdklab
2024-05-21 18:18 ` dpdklab
2024-05-21 18:19 ` dpdklab
2024-05-21 18:19 ` dpdklab
2024-05-21 18:19 ` dpdklab
2024-05-21 18:20 ` dpdklab
2024-05-21 18:20 ` dpdklab
2024-05-21 18:21 ` dpdklab
2024-05-21 18:22 ` dpdklab
2024-05-21 18:23 ` dpdklab
2024-05-21 18:23 ` dpdklab
2024-05-21 18:23 ` dpdklab
2024-05-21 18:24 ` dpdklab
2024-05-21 18:24 ` dpdklab
2024-05-21 18:24 ` dpdklab
2024-05-21 18:39 ` dpdklab
2024-05-21 18:41 ` dpdklab
2024-05-21 18:42 ` dpdklab
2024-05-21 18:43 ` dpdklab
2024-05-21 18:43 ` dpdklab
2024-05-21 18:43 ` dpdklab
2024-05-21 18:44 ` dpdklab
2024-05-21 18:45 ` dpdklab
2024-05-21 18:45 ` dpdklab
2024-05-21 18:46 ` dpdklab
2024-05-21 18:47 ` dpdklab
2024-05-21 18:50 ` dpdklab
2024-05-21 18:57 ` dpdklab
2024-05-21 18:58 ` dpdklab
2024-05-21 18:58 ` dpdklab
2024-05-21 19:02 ` dpdklab
2024-05-21 19:03 ` dpdklab
2024-05-21 19:04 ` dpdklab
2024-05-21 19:05 ` dpdklab
2024-05-21 19:06 ` dpdklab
2024-05-21 19:06 ` dpdklab
2024-05-21 19:06 ` dpdklab
2024-05-21 19:08 ` dpdklab
2024-05-21 19:09 ` dpdklab
2024-05-21 19:09 ` dpdklab
2024-05-21 19:10 ` dpdklab
2024-05-21 19:11 ` dpdklab
2024-05-21 19:16 ` dpdklab
2024-05-21 19:23 ` dpdklab
2024-05-21 21:25 ` dpdklab
2024-05-23 6:03 ` 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=202405211655.44LGtf5O595909@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).