From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140218-140228 [PATCH v15 11/11] net/tap: update documentation
Date: Wed, 22 May 2024 03:48:54 +0800 [thread overview]
Message-ID: <202405211948.44LJms20718294@localhost.localdomain> (raw)
In-Reply-To: <20240521201410.126116-12-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140228
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 21 May 2024 13:12:46 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 6f80df8cb0f889203d7cd27766abcc6ebc720e33
140218-140228 --> 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 20:17 UTC|newest]
Thread overview: 91+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240521201410.126116-12-stephen@networkplumber.org>
2024-05-21 19:48 ` qemudev [this message]
2024-05-21 19:53 ` qemudev
2024-05-21 20:16 ` |SUCCESS| pw140228 " checkpatch
2024-05-21 21:04 ` 0-day Robot
2024-05-21 21:57 ` |SUCCESS| pw140218-140228 [PATCH] [v15,11/11] net/tap: update docume dpdklab
2024-05-21 21:58 ` dpdklab
2024-05-21 21:59 ` dpdklab
2024-05-21 22:00 ` dpdklab
2024-05-21 22:00 ` dpdklab
2024-05-21 22:02 ` dpdklab
2024-05-21 22:02 ` dpdklab
2024-05-21 22:03 ` dpdklab
2024-05-21 22:03 ` dpdklab
2024-05-21 22:33 ` dpdklab
2024-05-21 22:34 ` dpdklab
2024-05-21 22:34 ` dpdklab
2024-05-21 22:34 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:35 ` dpdklab
2024-05-21 22:36 ` dpdklab
2024-05-21 22:36 ` dpdklab
2024-05-21 22:37 ` dpdklab
2024-05-21 22:37 ` dpdklab
2024-05-21 22:37 ` dpdklab
2024-05-21 22:37 ` dpdklab
2024-05-21 22:38 ` dpdklab
2024-05-21 22:38 ` dpdklab
2024-05-21 22:38 ` dpdklab
2024-05-21 22:38 ` dpdklab
2024-05-21 22:38 ` dpdklab
2024-05-21 22:39 ` dpdklab
2024-05-21 22:39 ` dpdklab
2024-05-21 22:39 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:40 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:41 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:42 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:43 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-21 22:44 ` dpdklab
2024-05-21 22:45 ` dpdklab
2024-05-21 22:45 ` dpdklab
2024-05-21 22:45 ` dpdklab
2024-05-21 22:45 ` dpdklab
2024-05-21 22:46 ` dpdklab
2024-05-21 22:47 ` dpdklab
2024-05-21 22:47 ` dpdklab
2024-05-21 22:48 ` dpdklab
2024-05-21 22:48 ` dpdklab
2024-05-21 22:49 ` dpdklab
2024-05-21 22:50 ` dpdklab
2024-05-21 22:50 ` dpdklab
2024-05-21 22:51 ` dpdklab
2024-05-21 22:58 ` dpdklab
2024-05-21 22:59 ` dpdklab
2024-05-21 23:00 ` dpdklab
2024-05-21 23:01 ` dpdklab
2024-05-21 23:04 ` dpdklab
2024-05-21 23:05 ` dpdklab
2024-05-21 23:19 ` dpdklab
2024-05-21 23:29 ` dpdklab
2024-05-21 23:35 ` dpdklab
2024-05-21 23:48 ` dpdklab
2024-05-21 23:50 ` dpdklab
2024-05-21 23:55 ` dpdklab
2024-05-23 6:08 ` 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=202405211948.44LJms20718294@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).