From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw140013-140015 [RFC 3/3] net/tap: use generic SW stats
Date: Fri, 10 May 2024 12:39:15 +0800 [thread overview]
Message-ID: <202405100439.44A4dFBB3682932@localhost.localdomain> (raw)
In-Reply-To: <20240510050507.14381-4-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/140015
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Thu, 9 May 2024 22:01:21 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 7e06c0de1952d3109a5b0c4779d7e7d8059c9d78
140013-140015 --> 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-10 5:07 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240510050507.14381-4-stephen@networkplumber.org>
2024-05-10 4:39 ` qemudev [this message]
2024-05-10 4:43 ` qemudev
2024-05-10 5:07 ` |SUCCESS| pw140015 " checkpatch
2024-05-10 6:04 ` |FAILURE| " 0-day Robot
2024-05-10 6:18 ` |SUCCESS| pw140013-140015 [PATCH] [RFC,3/3] net/tap: use generic SW dpdklab
2024-05-10 6:27 ` dpdklab
2024-05-10 6:28 ` dpdklab
2024-05-10 6:29 ` dpdklab
2024-05-10 6:29 ` dpdklab
2024-05-10 6:35 ` dpdklab
2024-05-10 6:35 ` dpdklab
2024-05-10 6:37 ` |FAILURE| " dpdklab
2024-05-10 6:37 ` dpdklab
2024-05-10 6:39 ` |SUCCESS| " dpdklab
2024-05-10 6:40 ` dpdklab
2024-05-10 6:40 ` |FAILURE| " dpdklab
2024-05-10 6:41 ` dpdklab
2024-05-10 6:41 ` dpdklab
2024-05-10 6:42 ` dpdklab
2024-05-10 6:42 ` dpdklab
2024-05-10 6:43 ` dpdklab
2024-05-10 6:43 ` |SUCCESS| " dpdklab
2024-05-10 6:44 ` |FAILURE| " dpdklab
2024-05-10 6:44 ` dpdklab
2024-05-10 6:44 ` |SUCCESS| " dpdklab
2024-05-10 6:44 ` |FAILURE| " dpdklab
2024-05-10 6:45 ` dpdklab
2024-05-10 6:45 ` dpdklab
2024-05-10 6:45 ` dpdklab
2024-05-10 6:46 ` dpdklab
2024-05-10 6:46 ` dpdklab
2024-05-10 6:47 ` dpdklab
2024-05-10 6:47 ` |SUCCESS| " dpdklab
2024-05-10 6:47 ` |FAILURE| " dpdklab
2024-05-10 6:48 ` dpdklab
2024-05-10 6:48 ` dpdklab
2024-05-10 6:48 ` dpdklab
2024-05-10 6:48 ` dpdklab
2024-05-10 6:48 ` dpdklab
2024-05-10 6:49 ` |SUCCESS| " dpdklab
2024-05-10 6:49 ` |FAILURE| " dpdklab
2024-05-10 6:49 ` dpdklab
2024-05-10 6:50 ` dpdklab
2024-05-10 6:50 ` dpdklab
2024-05-10 6:51 ` dpdklab
2024-05-10 6:51 ` |SUCCESS| " dpdklab
2024-05-10 6:51 ` |FAILURE| " dpdklab
2024-05-10 6:51 ` dpdklab
2024-05-10 6:51 ` |SUCCESS| " dpdklab
2024-05-10 6:52 ` |FAILURE| " dpdklab
2024-05-10 6:52 ` dpdklab
2024-05-10 6:52 ` dpdklab
2024-05-10 6:52 ` |SUCCESS| " dpdklab
2024-05-10 6:53 ` |FAILURE| " dpdklab
2024-05-10 6:53 ` dpdklab
2024-05-10 6:53 ` dpdklab
2024-05-10 6:54 ` dpdklab
2024-05-10 6:55 ` |SUCCESS| " dpdklab
2024-05-10 6:56 ` |FAILURE| " dpdklab
2024-05-10 6:56 ` dpdklab
2024-05-10 6:56 ` dpdklab
2024-05-10 6:56 ` dpdklab
2024-05-10 6:57 ` dpdklab
2024-05-10 6:57 ` dpdklab
2024-05-10 6:57 ` |SUCCESS| " dpdklab
2024-05-10 6:57 ` |FAILURE| " dpdklab
2024-05-10 7:00 ` dpdklab
2024-05-10 7:00 ` dpdklab
2024-05-10 7:01 ` dpdklab
2024-05-10 7:01 ` dpdklab
2024-05-10 7:02 ` dpdklab
2024-05-10 7:03 ` dpdklab
2024-05-10 7:04 ` dpdklab
2024-05-10 7:04 ` dpdklab
2024-05-10 7:04 ` dpdklab
2024-05-10 7:05 ` dpdklab
2024-05-10 7:06 ` dpdklab
2024-05-10 7:06 ` dpdklab
2024-05-10 7:07 ` dpdklab
2024-05-10 7:59 ` |SUCCESS| " dpdklab
2024-05-10 8:34 ` dpdklab
2024-05-10 8:35 ` |FAILURE| " dpdklab
2024-05-10 8:36 ` |SUCCESS| " dpdklab
2024-05-10 8:40 ` dpdklab
2024-05-10 8:40 ` dpdklab
2024-05-10 8:50 ` dpdklab
2024-05-10 8:59 ` |FAILURE| " dpdklab
2024-05-10 9:03 ` |SUCCESS| " dpdklab
2024-05-10 9:38 ` 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=202405100439.44A4dFBB3682932@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).