From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw126218 [PATCH] usertools: enhance CPU layout
Date: Tue, 18 Apr 2023 13:49:21 +0800 [thread overview]
Message-ID: <202304180549.33I5nLfT3411465@localhost.localdomain> (raw)
In-Reply-To: <1681795541-68384-1-git-send-email-wenzhuo.lu@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/126218
_Compilation OK_
Submitter: Wenzhuo Lu <wenzhuo.lu@intel.com>
Date: Tue, 18 Apr 2023 13:25:41 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3b3fef9de22af80d173453ab65a80b01ce38cbfd
126218 --> 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-04-18 6:03 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1681795541-68384-1-git-send-email-wenzhuo.lu@intel.com>
2023-04-18 5:49 ` qemudev [this message]
2023-04-18 5:53 ` qemudev
2023-04-18 5:59 ` |WARNING| " checkpatch
2023-04-18 6:59 ` |SUCCESS| " 0-day Robot
2023-04-18 19:44 dpdklab
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 19:44 dpdklab
2023-04-18 18:35 dpdklab
2023-04-18 18:34 dpdklab
2023-04-18 13:40 dpdklab
2023-04-18 13:29 dpdklab
2023-04-18 12:54 dpdklab
2023-04-18 12:16 dpdklab
2023-04-18 9:43 dpdklab
2023-04-18 9:26 dpdklab
2023-04-18 9:23 dpdklab
2023-04-18 9:21 dpdklab
2023-04-18 9:16 dpdklab
2023-04-18 9:11 dpdklab
2023-04-18 9:08 dpdklab
2023-04-18 9:03 dpdklab
2023-04-18 9:02 dpdklab
2023-04-18 9:01 dpdklab
2023-04-18 9:00 dpdklab
2023-04-18 8:58 dpdklab
2023-04-18 8:56 dpdklab
2023-04-18 8:50 dpdklab
2023-04-18 8:46 dpdklab
2023-04-18 8:45 dpdklab
2023-04-18 8:35 dpdklab
2023-04-18 8:31 dpdklab
2023-04-18 8:27 dpdklab
2023-04-18 8:24 dpdklab
2023-04-18 8:24 dpdklab
2023-04-18 8:20 dpdklab
2023-04-18 8:20 dpdklab
2023-04-18 8:19 dpdklab
2023-04-18 8:18 dpdklab
2023-04-18 8:17 dpdklab
2023-04-18 8:13 dpdklab
2023-04-18 8:11 dpdklab
2023-04-18 8:08 dpdklab
2023-04-18 8:08 dpdklab
2023-04-18 8:07 dpdklab
2023-04-18 8:05 dpdklab
2023-04-18 8:04 dpdklab
2023-04-18 8:00 dpdklab
2023-04-18 8:00 dpdklab
2023-04-18 7:53 dpdklab
2023-04-18 7:41 dpdklab
2023-04-18 7:29 dpdklab
2023-04-18 7:20 dpdklab
2023-04-18 7:18 dpdklab
2023-04-18 7:16 dpdklab
2023-04-18 7:11 dpdklab
2023-04-18 7:06 dpdklab
2023-04-18 7:04 dpdklab
2023-04-18 6:58 dpdklab
2023-04-18 6:56 dpdklab
2023-04-18 6:56 dpdklab
2023-04-18 6:55 dpdklab
2023-04-18 6:50 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=202304180549.33I5nLfT3411465@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).