From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw143566 [PATCH v1 1/1] buildtools: add VSCode configuration generator
Date: Mon, 2 Sep 2024 19:51:08 +0800 [thread overview]
Message-ID: <202409021151.482Bp85g128066@localhost.localdomain> (raw)
In-Reply-To: <0c924fc63d269e51c1df95f72a885646edff5894.1725279341.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/143566
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Mon, 2 Sep 2024 13:17:48 +0100
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: cb9187bc5c2b4bab0ad80194ac3b60491de14e8c
143566 --> 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-09-02 12:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0c924fc63d269e51c1df95f72a885646edff5894.1725279341.git.anatoly.burakov@intel.com>
2024-09-02 11:51 ` qemudev [this message]
2024-09-02 11:55 ` qemudev
2024-09-02 12:19 ` checkpatch
2024-09-02 13:04 ` 0-day Robot
2024-09-02 15:42 ` |PENDING| pw143566 [PATCH] [v1,1/1] buildtools: add VSCode configura dpdklab
2024-09-02 15:45 ` |SUCCESS| " dpdklab
2024-09-02 15:46 ` |PENDING| " dpdklab
2024-09-02 15:46 ` dpdklab
2024-09-02 15:51 ` |SUCCESS| " dpdklab
2024-09-02 15:51 ` dpdklab
2024-09-02 15:51 ` dpdklab
2024-09-02 15:51 ` dpdklab
2024-09-02 15:53 ` dpdklab
2024-09-02 15:54 ` dpdklab
2024-09-02 15:54 ` dpdklab
2024-09-02 15:56 ` dpdklab
2024-09-02 15:56 ` dpdklab
2024-09-02 15:57 ` dpdklab
2024-09-02 15:57 ` dpdklab
2024-09-02 16:01 ` dpdklab
2024-09-02 16:05 ` dpdklab
2024-09-02 16:06 ` dpdklab
2024-09-02 16:06 ` dpdklab
2024-09-02 16:07 ` dpdklab
2024-09-02 16:35 ` dpdklab
2024-09-02 16:35 ` dpdklab
2024-09-02 16:35 ` dpdklab
2024-09-02 16:35 ` dpdklab
2024-09-02 16:36 ` dpdklab
2024-09-02 16:36 ` dpdklab
2024-09-02 16:36 ` dpdklab
2024-09-02 16:37 ` dpdklab
2024-09-02 16:37 ` dpdklab
2024-09-02 17:28 ` dpdklab
2024-09-02 17:43 ` |PENDING| " dpdklab
2024-09-02 18:06 ` |SUCCESS| " dpdklab
2024-09-02 18:38 ` dpdklab
2024-09-02 19:12 ` dpdklab
2024-09-02 19:13 ` dpdklab
2024-09-02 19:25 ` dpdklab
2024-09-02 20:04 ` dpdklab
2024-09-18 19:54 ` dpdklab
2024-09-18 20:13 ` dpdklab
2024-09-18 20:26 ` dpdklab
2024-09-18 20:44 ` 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=202409021151.482Bp85g128066@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).