From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139814-139825 [PATCH v12 12/12] net/tap: update documentation
Date: Fri, 3 May 2024 05:12:52 +0800 [thread overview]
Message-ID: <202405022112.442LCqEW606383@localhost.localdomain> (raw)
In-Reply-To: <20240502213618.11391-13-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139825
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 2 May 2024 14:31:37 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
139814-139825 --> 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-02 21:40 UTC|newest]
Thread overview: 93+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240502213618.11391-13-stephen@networkplumber.org>
2024-05-02 21:12 ` qemudev [this message]
2024-05-02 21:17 ` qemudev
2024-05-02 22:23 ` |SUCCESS| pw139825 " 0-day Robot
2024-05-03 6:23 ` |SUCCESS| pw139814-139825 [PATCH] [v12,12/12] net/tap: update docume dpdklab
2024-05-03 6:32 ` dpdklab
2024-05-03 6:32 ` dpdklab
2024-05-03 6:33 ` dpdklab
2024-05-03 6:47 ` dpdklab
2024-05-03 6:51 ` dpdklab
2024-05-03 6:51 ` dpdklab
2024-05-03 6:52 ` dpdklab
2024-05-03 6:53 ` dpdklab
2024-05-03 6:55 ` dpdklab
2024-05-03 6:55 ` dpdklab
2024-05-03 6:57 ` dpdklab
2024-05-03 6:58 ` dpdklab
2024-05-03 6:58 ` dpdklab
2024-05-03 6:59 ` dpdklab
2024-05-03 6:59 ` dpdklab
2024-05-03 7:01 ` dpdklab
2024-05-03 7:02 ` dpdklab
2024-05-03 7:03 ` dpdklab
2024-05-03 7:03 ` dpdklab
2024-05-03 7:04 ` dpdklab
2024-05-03 7:04 ` dpdklab
2024-05-03 7:16 ` dpdklab
2024-05-03 7:16 ` dpdklab
2024-05-03 7:16 ` dpdklab
2024-05-03 7:17 ` dpdklab
2024-05-03 7:17 ` dpdklab
2024-05-03 7:18 ` dpdklab
2024-05-03 7:18 ` dpdklab
2024-05-03 7:19 ` dpdklab
2024-05-03 7:25 ` dpdklab
2024-05-03 7:35 ` dpdklab
2024-05-03 7:43 ` dpdklab
2024-05-03 7:56 ` dpdklab
2024-05-03 7:57 ` dpdklab
2024-05-03 7:59 ` dpdklab
2024-05-03 8:00 ` dpdklab
2024-05-03 8:06 ` dpdklab
2024-05-03 8:11 ` dpdklab
2024-05-03 8:11 ` dpdklab
2024-05-03 8:13 ` dpdklab
2024-05-03 8:16 ` dpdklab
2024-05-03 8:16 ` dpdklab
2024-05-03 8:18 ` dpdklab
2024-05-03 8:19 ` |SUCCESS| pw139825 [PATCH v12 12/12] net/tap: update documentation checkpatch
2024-05-03 8:19 ` |SUCCESS| pw139814-139825 [PATCH] [v12,12/12] net/tap: update docume dpdklab
2024-05-03 8:20 ` dpdklab
2024-05-03 8:22 ` dpdklab
2024-05-03 8:23 ` dpdklab
2024-05-03 8:24 ` dpdklab
2024-05-03 8:25 ` dpdklab
2024-05-03 8:27 ` dpdklab
2024-05-03 8:28 ` dpdklab
2024-05-03 8:28 ` dpdklab
2024-05-03 8:31 ` dpdklab
2024-05-03 8:31 ` dpdklab
2024-05-03 8:31 ` dpdklab
2024-05-03 8:32 ` dpdklab
2024-05-03 8:34 ` dpdklab
2024-05-03 8:34 ` dpdklab
2024-05-03 8:34 ` dpdklab
2024-05-03 8:35 ` dpdklab
2024-05-03 8:35 ` dpdklab
2024-05-03 8:38 ` dpdklab
2024-05-03 8:38 ` dpdklab
2024-05-03 8:40 ` dpdklab
2024-05-03 8:40 ` dpdklab
2024-05-03 8:45 ` dpdklab
2024-05-03 8:47 ` dpdklab
2024-05-03 8:48 ` dpdklab
2024-05-03 8:49 ` dpdklab
2024-05-03 8:50 ` dpdklab
2024-05-03 8:58 ` dpdklab
2024-05-03 9:02 ` dpdklab
2024-05-03 9:16 ` dpdklab
2024-05-03 9:17 ` dpdklab
2024-05-03 9:37 ` dpdklab
2024-05-03 9:45 ` dpdklab
2024-05-03 9:48 ` |SUCCESS| pw139825 [PATCH v12 12/12] net/tap: update documentation checkpatch
2024-05-03 9:56 ` checkpatch
2024-05-03 10:27 ` |SUCCESS| pw139814-139825 [PATCH] [v12,12/12] net/tap: update docume dpdklab
2024-05-03 10:38 ` dpdklab
2024-05-03 10:56 ` dpdklab
2024-05-03 18:17 ` dpdklab
2024-05-05 3:06 ` dpdklab
2024-05-05 3:12 ` dpdklab
2024-05-05 3:16 ` dpdklab
2024-05-05 3:20 ` dpdklab
2024-05-05 3:39 ` dpdklab
2024-05-06 10:37 ` 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=202405022112.442LCqEW606383@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).