From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139740 [PATCH] net/af_packet: fix statistics
Date: Tue, 30 Apr 2024 23:15:38 +0800 [thread overview]
Message-ID: <202404301515.43UFFcQ23326610@localhost.localdomain> (raw)
In-Reply-To: <20240430154129.7347-1-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139740
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 30 Apr 2024 08:39:46 -0700
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 70fef0ac8fa33eebc9c5c95844466544f35e35f9
139740 --> 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-04-30 15:43 UTC|newest]
Thread overview: 90+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240430154129.7347-1-stephen@networkplumber.org>
2024-04-30 15:15 ` qemudev [this message]
2024-04-30 15:19 ` qemudev
2024-04-30 16:40 ` dpdklab
2024-04-30 16:41 ` dpdklab
2024-04-30 16:41 ` dpdklab
2024-04-30 16:42 ` dpdklab
2024-04-30 16:42 ` dpdklab
2024-04-30 16:43 ` dpdklab
2024-04-30 16:43 ` dpdklab
2024-04-30 16:43 ` dpdklab
2024-04-30 16:44 ` 0-day Robot
2024-04-30 16:44 ` dpdklab
2024-04-30 16:44 ` dpdklab
2024-04-30 16:44 ` dpdklab
2024-04-30 16:45 ` dpdklab
2024-04-30 16:45 ` dpdklab
2024-04-30 16:46 ` dpdklab
2024-04-30 16:46 ` |FAILURE| " dpdklab
2024-04-30 16:46 ` dpdklab
2024-04-30 16:47 ` |SUCCESS| " dpdklab
2024-04-30 16:47 ` dpdklab
2024-04-30 16:48 ` dpdklab
2024-04-30 16:48 ` dpdklab
2024-04-30 16:48 ` dpdklab
2024-04-30 16:49 ` dpdklab
2024-04-30 16:49 ` dpdklab
2024-04-30 16:49 ` dpdklab
2024-04-30 16:50 ` dpdklab
2024-04-30 16:50 ` dpdklab
2024-04-30 16:50 ` |FAILURE| " dpdklab
2024-04-30 16:50 ` |SUCCESS| " dpdklab
2024-04-30 16:51 ` dpdklab
2024-04-30 16:51 ` dpdklab
2024-04-30 16:52 ` dpdklab
2024-04-30 16:52 ` dpdklab
2024-04-30 16:53 ` dpdklab
2024-04-30 16:53 ` dpdklab
2024-04-30 16:53 ` dpdklab
2024-04-30 16:54 ` dpdklab
2024-04-30 16:54 ` dpdklab
2024-04-30 16:55 ` |FAILURE| " dpdklab
2024-04-30 16:55 ` dpdklab
2024-04-30 16:55 ` |SUCCESS| " dpdklab
2024-04-30 16:56 ` |FAILURE| " dpdklab
2024-04-30 16:56 ` |SUCCESS| " dpdklab
2024-04-30 16:56 ` dpdklab
2024-04-30 16:57 ` dpdklab
2024-04-30 16:57 ` dpdklab
2024-04-30 16:57 ` |FAILURE| " dpdklab
2024-04-30 16:57 ` dpdklab
2024-04-30 16:57 ` dpdklab
2024-04-30 16:57 ` |SUCCESS| " dpdklab
2024-04-30 16:58 ` dpdklab
2024-04-30 16:58 ` dpdklab
2024-04-30 16:58 ` dpdklab
2024-04-30 16:58 ` dpdklab
2024-04-30 16:59 ` |FAILURE| " dpdklab
2024-04-30 16:59 ` |SUCCESS| " dpdklab
2024-04-30 16:59 ` dpdklab
2024-04-30 17:00 ` |FAILURE| " dpdklab
2024-04-30 17:00 ` |SUCCESS| " dpdklab
2024-04-30 17:02 ` dpdklab
2024-04-30 17:03 ` dpdklab
2024-04-30 17:03 ` dpdklab
2024-04-30 17:04 ` dpdklab
2024-04-30 17:04 ` dpdklab
2024-04-30 17:04 ` dpdklab
2024-04-30 17:05 ` dpdklab
2024-04-30 17:05 ` dpdklab
2024-04-30 17:07 ` dpdklab
2024-04-30 17:09 ` |FAILURE| " dpdklab
2024-04-30 17:10 ` |SUCCESS| " dpdklab
2024-04-30 17:12 ` dpdklab
2024-04-30 17:12 ` dpdklab
2024-04-30 17:13 ` dpdklab
2024-04-30 17:15 ` dpdklab
2024-04-30 17:17 ` dpdklab
2024-04-30 17:18 ` dpdklab
2024-04-30 17:20 ` dpdklab
2024-04-30 17:22 ` dpdklab
2024-04-30 17:24 ` dpdklab
2024-04-30 17:24 ` dpdklab
2024-04-30 17:30 ` dpdklab
2024-04-30 17:33 ` dpdklab
2024-04-30 17:34 ` dpdklab
2024-04-30 17:37 ` dpdklab
2024-04-30 17:37 ` |FAILURE| " dpdklab
2024-04-30 17:39 ` |SUCCESS| " dpdklab
2024-04-30 17:39 ` dpdklab
2024-04-30 17:42 ` 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=202404301515.43UFFcQ23326610@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).