From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138167 [PATCH v4] tap: do not duplicate fd's
Date: Tue, 12 Mar 2024 03:26:39 +0800 [thread overview]
Message-ID: <202403111926.42BJQda82625742@localhost.localdomain> (raw)
In-Reply-To: <20240311194543.39690-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138167
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Mon, 11 Mar 2024 12:45:12 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 49873fda52c3decea9a2fb06afb3a17164a656e9
138167 --> 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-03-11 19:51 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240311194543.39690-1-stephen@networkplumber.org>
2024-03-11 19:26 ` qemudev [this message]
2024-03-11 19:31 ` qemudev
2024-03-11 19:46 ` checkpatch
2024-03-11 20:27 ` |SUCCESS| pw138167 [PATCH] [v4] " dpdklab
2024-03-11 20:27 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:28 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:29 ` dpdklab
2024-03-11 20:30 ` dpdklab
2024-03-11 20:30 ` dpdklab
2024-03-11 20:30 ` dpdklab
2024-03-11 20:30 ` dpdklab
2024-03-11 20:30 ` dpdklab
2024-03-11 20:31 ` dpdklab
2024-03-11 20:31 ` dpdklab
2024-03-11 20:31 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:32 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:33 ` dpdklab
2024-03-11 20:34 ` dpdklab
2024-03-11 20:34 ` dpdklab
2024-03-11 20:34 ` dpdklab
2024-03-11 20:34 ` dpdklab
2024-03-11 20:34 ` dpdklab
2024-03-11 20:35 ` dpdklab
2024-03-11 20:35 ` dpdklab
2024-03-11 20:35 ` dpdklab
2024-03-11 20:35 ` dpdklab
2024-03-11 20:35 ` dpdklab
2024-03-11 20:36 ` dpdklab
2024-03-11 20:36 ` dpdklab
2024-03-11 20:37 ` dpdklab
2024-03-11 20:37 ` dpdklab
2024-03-11 20:38 ` dpdklab
2024-03-11 20:38 ` dpdklab
2024-03-11 20:40 ` dpdklab
2024-03-11 20:41 ` dpdklab
2024-03-11 20:42 ` |SUCCESS| pw138167 [PATCH v4] " 0-day Robot
2024-03-11 20:43 ` |SUCCESS| pw138167 [PATCH] [v4] " dpdklab
2024-03-11 20:43 ` dpdklab
2024-03-11 20:44 ` dpdklab
2024-03-11 20:47 ` dpdklab
2024-03-11 20:48 ` dpdklab
2024-03-11 20:58 ` dpdklab
2024-03-11 21:45 ` dpdklab
2024-03-12 0:20 ` dpdklab
2024-03-12 0:21 ` dpdklab
2024-03-12 0:27 ` dpdklab
2024-03-12 0:29 ` dpdklab
2024-03-15 5:46 ` dpdklab
2024-03-15 6:15 ` 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=202403111926.42BJQda82625742@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).