From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148922 [PATCH v3 1/1] devtools: add DPDK build directory setup script
Date: Fri, 29 Nov 2024 18:20:01 +0800 [thread overview]
Message-ID: <202411291020.4ATAK1pd3695746@localhost.localdomain> (raw)
In-Reply-To: <373adbe0cd8495b79882dbe44481ced550026e3f.1732719618.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148922
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 27 Nov 2024 15:01:37 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4843aacb0d1201fef37e8a579fcd8baec4acdf98
148922 --> 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 prev parent reply other threads:[~2024-11-29 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <373adbe0cd8495b79882dbe44481ced550026e3f.1732719618.git.anatoly.burakov@intel.com>
2024-11-27 15:03 ` checkpatch
2024-11-27 15:31 ` |PENDING| pw148922 [PATCH] [v3,1/1] devtools: add DPDK build directo dpdklab
2024-11-27 15:40 ` |SUCCESS| " dpdklab
2024-11-27 15:50 ` dpdklab
2024-11-27 15:52 ` dpdklab
2024-11-27 16:03 ` |SUCCESS| pw148922 [PATCH v3 1/1] devtools: add DPDK build directory setup script 0-day Robot
2024-11-27 16:16 ` |SUCCESS| pw148922 [PATCH] [v3,1/1] devtools: add DPDK build directo dpdklab
2024-11-27 16:24 ` dpdklab
2024-11-27 16:30 ` dpdklab
2024-11-27 16:35 ` dpdklab
2024-11-27 17:14 ` dpdklab
2024-11-27 17:23 ` dpdklab
2024-11-27 17:42 ` dpdklab
2024-11-27 17:54 ` dpdklab
2024-11-29 8:03 ` |SUCCESS| pw148922 [PATCH v3 1/1] devtools: add DPDK build directory setup script qemudev
2024-11-29 8:04 ` qemudev
2024-11-29 10:20 ` qemudev [this message]
2024-11-29 10:20 ` qemudev
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=202411291020.4ATAK1pd3695746@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).