From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw133973-133994 [PATCH v6 23/23] dts: add doc generation
Date: Wed, 8 Nov 2023 20:38:28 +0800 [thread overview]
Message-ID: <202311081238.3A8CcScr2336034@localhost.localdomain> (raw)
In-Reply-To: <20231108125324.191005-23-juraj.linkes@pantheon.tech>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/133994
_Compilation OK_
Submitter: Juraj Linkeš <juraj.linkes@pantheon.tech>
Date: Wed, 8 Nov 2023 13:53:02 +0100
DPDK git baseline: Repo:dpdk-next-baseband
Branch: for-main
CommitID: ff4cb2dcc1385bfa74085cd048d2f35c4230e466
133973-133994 --> 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-11-08 12:59 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231108125324.191005-23-juraj.linkes@pantheon.tech>
2023-11-08 12:38 ` qemudev [this message]
2023-11-08 12:42 ` qemudev
2023-11-08 12:58 ` |WARNING| pw133994 " checkpatch
2023-11-08 14:22 ` |SUCCESS| " 0-day Robot
2023-11-08 13:31 |SUCCESS| pw133973-133994 [PATCH] [v6,23/23] " dpdklab
2023-11-08 13:32 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:36 dpdklab
2023-11-08 13:37 dpdklab
2023-11-08 13:37 dpdklab
2023-11-08 13:37 dpdklab
2023-11-08 13:38 dpdklab
2023-11-08 13:38 dpdklab
2023-11-08 13:38 dpdklab
2023-11-08 13:39 dpdklab
2023-11-08 13:39 dpdklab
2023-11-08 13:39 dpdklab
2023-11-08 13:39 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:40 dpdklab
2023-11-08 13:41 dpdklab
2023-11-08 13:41 dpdklab
2023-11-08 13:41 dpdklab
2023-11-08 13:41 dpdklab
2023-11-08 13:41 dpdklab
2023-11-08 13:42 dpdklab
2023-11-08 13:43 dpdklab
2023-11-08 13:43 dpdklab
2023-11-08 13:44 dpdklab
2023-11-08 13:44 dpdklab
2023-11-08 13:44 dpdklab
2023-11-08 13:44 dpdklab
2023-11-08 13:44 dpdklab
2023-11-08 13:45 dpdklab
2023-11-08 13:45 dpdklab
2023-11-08 13:45 dpdklab
2023-11-08 13:45 dpdklab
2023-11-08 13:46 dpdklab
2023-11-08 13:46 dpdklab
2023-11-08 13:46 dpdklab
2023-11-08 13:48 dpdklab
2023-11-08 14:00 dpdklab
2023-11-08 14:04 dpdklab
2023-11-08 16:23 dpdklab
2023-11-08 21:33 dpdklab
2023-11-09 10:32 dpdklab
2023-11-09 11:06 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=202311081238.3A8CcScr2336034@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).