From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148942 [PATCH v4] dts: remove nested html dir for API doc
Date: Fri, 29 Nov 2024 19:25:11 +0800 [thread overview]
Message-ID: <202411291125.4ATBPBJh3760266@localhost.localdomain> (raw)
In-Reply-To: <20241129115528.194137-1-thomas@monjalon.net>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148942
_Compilation OK_
Submitter: Thomas Monjalon <thomas@monjalon.net>
Date: Fri, 29 Nov 2024 12:54:26 +0100
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4843aacb0d1201fef37e8a579fcd8baec4acdf98
148942 --> 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-11-29 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241129115528.194137-1-thomas@monjalon.net>
2024-11-29 11:25 ` qemudev [this message]
2024-11-29 11:29 ` qemudev
2024-11-29 11:55 ` checkpatch
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=202411291125.4ATBPBJh3760266@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).