From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw139705 [RFC v2] net/af_packet: make stats reset reliable
Date: Fri, 26 Apr 2024 22:13:31 +0800 [thread overview]
Message-ID: <202404261413.43QEDVBL2496959@localhost.localdomain> (raw)
In-Reply-To: <20240426143848.2280689-1-ferruh.yigit@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/139705
_Compilation OK_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Fri, 26 Apr 2024 15:38:48 +0100
DPDK git baseline: Repo:dpdk-next-net
Branch: main
CommitID: 9e0dea69a085f7a5931e079d9aaa3ae944e8aa34
139705 --> 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-26 14:41 UTC|newest]
Thread overview: 86+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240426143848.2280689-1-ferruh.yigit@amd.com>
2024-04-26 14:13 ` qemudev [this message]
2024-04-26 14:17 ` qemudev
2024-04-26 15:46 ` |SUCCESS| pw139705 [PATCH] [RFC,v2] net/af_packet: make stats reset dpdklab
2024-04-26 15:57 ` dpdklab
2024-04-26 16:03 ` dpdklab
2024-04-26 16:04 ` dpdklab
2024-04-26 16:04 ` dpdklab
2024-04-26 16:06 ` dpdklab
2024-04-26 16:06 ` dpdklab
2024-04-26 16:07 ` dpdklab
2024-04-26 16:07 ` dpdklab
2024-04-26 16:13 ` dpdklab
2024-04-26 16:13 ` dpdklab
2024-04-26 16:13 ` dpdklab
2024-04-26 16:14 ` dpdklab
2024-04-26 16:15 ` dpdklab
2024-04-26 16:15 ` dpdklab
2024-04-26 16:15 ` dpdklab
2024-04-26 16:16 ` dpdklab
2024-04-26 16:16 ` dpdklab
2024-04-26 16:16 ` dpdklab
2024-04-26 16:17 ` dpdklab
2024-04-26 16:17 ` dpdklab
2024-04-26 16:18 ` dpdklab
2024-04-26 16:19 ` dpdklab
2024-04-26 16:19 ` dpdklab
2024-04-26 16:22 ` dpdklab
2024-04-26 16:23 ` dpdklab
2024-04-26 16:23 ` dpdklab
2024-04-26 16:23 ` dpdklab
2024-04-26 16:23 ` dpdklab
2024-04-26 16:24 ` dpdklab
2024-04-26 16:24 ` dpdklab
2024-04-26 16:24 ` dpdklab
2024-04-26 16:24 ` dpdklab
2024-04-26 16:25 ` dpdklab
2024-04-26 16:25 ` dpdklab
2024-04-26 16:25 ` dpdklab
2024-04-26 16:25 ` dpdklab
2024-04-26 16:26 ` dpdklab
2024-04-26 16:28 ` dpdklab
2024-04-26 16:29 ` dpdklab
2024-04-26 16:29 ` dpdklab
2024-04-26 16:30 ` dpdklab
2024-04-26 16:30 ` dpdklab
2024-04-26 16:37 ` dpdklab
2024-04-26 16:37 ` dpdklab
2024-04-26 16:38 ` dpdklab
2024-04-26 16:39 ` dpdklab
2024-04-26 16:39 ` dpdklab
2024-04-26 16:42 ` dpdklab
2024-04-26 16:43 ` dpdklab
2024-04-26 16:44 ` dpdklab
2024-04-26 16:45 ` dpdklab
2024-04-26 16:45 ` dpdklab
2024-04-26 16:46 ` dpdklab
2024-04-26 16:46 ` dpdklab
2024-04-26 16:48 ` dpdklab
2024-04-26 16:48 ` dpdklab
2024-04-26 16:49 ` dpdklab
2024-04-26 16:51 ` dpdklab
2024-04-26 16:52 ` dpdklab
2024-04-26 16:52 ` dpdklab
2024-04-26 16:52 ` dpdklab
2024-04-26 16:54 ` dpdklab
2024-04-26 16:54 ` dpdklab
2024-04-26 16:55 ` dpdklab
2024-04-26 16:55 ` dpdklab
2024-04-26 16:56 ` dpdklab
2024-04-26 16:58 ` dpdklab
2024-04-26 16:58 ` dpdklab
2024-04-26 17:01 ` dpdklab
2024-04-26 17:01 ` dpdklab
2024-04-26 17:05 ` dpdklab
2024-04-26 17:06 ` dpdklab
2024-04-26 17:06 ` dpdklab
2024-04-26 17:06 ` dpdklab
2024-04-26 17:13 ` dpdklab
2024-04-26 17:14 ` dpdklab
2024-04-26 17:24 ` dpdklab
2024-04-26 17:27 ` |FAILURE| " dpdklab
2024-04-26 17:29 ` |SUCCESS| " dpdklab
2024-04-26 17:30 ` dpdklab
2024-04-26 17:58 ` dpdklab
2024-04-26 18:09 ` dpdklab
2024-04-26 18:34 ` 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=202404261413.43QEDVBL2496959@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).