From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw144149-144163 [PATCH v23 15/15] doc: add release note about log library
Date: Wed, 18 Sep 2024 12:35:14 +0800 [thread overview]
Message-ID: <202409180435.48I4ZEgq2584879@localhost.localdomain> (raw)
In-Reply-To: <20240918045830.3798-16-stephen@networkplumber.org>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/144163
_Compilation OK_
Submitter: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 17 Sep 2024 21:56:06 -0700
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 41dd9a6bc2d9c6e20e139ad713cc9d172572dd43
144149-144163 --> 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-18 5:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240918045830.3798-16-stephen@networkplumber.org>
2024-09-18 4:35 ` qemudev [this message]
2024-09-18 4:39 ` qemudev
2024-09-18 5:02 ` |SUCCESS| pw144163 " checkpatch
2024-09-18 6:04 ` 0-day Robot
2024-09-18 8:50 ` |SUCCESS| pw144149-144163 [PATCH] [v23,15/15] doc: add release note dpdklab
2024-09-18 8:54 ` dpdklab
2024-09-18 9:22 ` dpdklab
2024-09-18 9:22 ` dpdklab
2024-09-18 10:48 ` |FAILURE| " dpdklab
2024-09-18 11:28 ` |PENDING| " dpdklab
2024-09-18 11:39 ` |SUCCESS| " dpdklab
2024-09-18 11:40 ` dpdklab
2024-09-18 11:43 ` |PENDING| " dpdklab
2024-09-18 11:49 ` dpdklab
2024-09-18 12:07 ` |SUCCESS| " dpdklab
2024-09-18 13:46 ` dpdklab
2024-09-18 13:49 ` dpdklab
2024-09-18 14:08 ` dpdklab
2024-09-18 14:35 ` dpdklab
2024-09-19 1:22 ` dpdklab
2024-09-22 13:16 ` dpdklab
2024-09-22 13:28 ` 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=202409180435.48I4ZEgq2584879@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).