From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133799-133805 [PATCH v3 7/7] Section 6: Glossary
Date: Fri, 3 Nov 2023 11:43:41 +0800 [thread overview]
Message-ID: <202311030343.3A33hfGR2777863@localhost.localdomain> (raw)
In-Reply-To: <20231103040202.2849-8-dave@youngcopy.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133805
_Compilation OK_
Submitter: David Young <dave@youngcopy.com>
Date: Fri, 3 Nov 2023 00:01:47 -0400
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: e9555aad006a739de9ae2a14a94128931634eea0
133799-133805 --> 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:[~2023-11-03 4:04 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231103040202.2849-8-dave@youngcopy.com>
2023-11-03 3:43 ` qemudev [this message]
2023-11-03 3:47 ` qemudev
2023-11-03 4:04 ` |WARNING| pw133805 " checkpatch
2023-11-03 5:19 ` |FAILURE| " 0-day Robot
2023-11-03 8:53 |SUCCESS| pw133799-133805 [PATCH] [v3,7/7] " dpdklab
2023-11-03 9:23 dpdklab
2023-11-03 9:24 dpdklab
2023-11-03 9:24 dpdklab
2023-11-03 9:25 dpdklab
2023-11-03 9:26 dpdklab
2023-11-03 9:26 dpdklab
2023-11-03 9:27 dpdklab
2023-11-03 9:27 dpdklab
2023-11-03 9:37 dpdklab
2023-11-03 9:37 dpdklab
2023-11-03 10:06 dpdklab
2023-11-03 10:08 dpdklab
2023-11-03 10:09 dpdklab
2023-11-03 10:10 dpdklab
2023-11-03 10:15 dpdklab
2023-11-03 10:17 dpdklab
2023-11-03 10:17 dpdklab
2023-11-03 10:17 dpdklab
2023-11-03 10:17 dpdklab
2023-11-03 10:18 dpdklab
2023-11-03 10:18 dpdklab
2023-11-03 10:18 dpdklab
2023-11-03 10:18 dpdklab
2023-11-03 10:18 dpdklab
2023-11-03 10:23 dpdklab
2023-11-03 10:23 dpdklab
2023-11-03 10:24 dpdklab
2023-11-03 10:24 dpdklab
2023-11-03 10:24 dpdklab
2023-11-03 10:25 dpdklab
2023-11-03 10:25 dpdklab
2023-11-03 10:25 dpdklab
2023-11-03 10:25 dpdklab
2023-11-03 10:25 dpdklab
2023-11-03 10:26 dpdklab
2023-11-03 10:26 dpdklab
2023-11-03 10:28 dpdklab
2023-11-03 10:28 dpdklab
2023-11-03 10:28 dpdklab
2023-11-03 10:29 dpdklab
2023-11-03 10:34 dpdklab
2023-11-03 10:35 dpdklab
2023-11-03 10:35 dpdklab
2023-11-03 10:39 dpdklab
2023-11-03 10:39 dpdklab
2023-11-03 10:41 dpdklab
2023-11-03 10:42 dpdklab
2023-11-03 10:42 dpdklab
2023-11-03 10:42 dpdklab
2023-11-03 10:43 dpdklab
2023-11-03 10:49 dpdklab
2023-11-03 10:53 dpdklab
2023-11-03 10:58 dpdklab
2023-11-03 10:59 dpdklab
2023-11-03 12:50 dpdklab
2023-11-03 13:04 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=202311030343.3A33hfGR2777863@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).