From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw146864-146904 [PATCH v4 42/42] vdpa/sfc: use rte strerror
Date: Wed, 23 Oct 2024 16:02:48 +0800 [thread overview]
Message-ID: <202410230802.49N82mt5452301@localhost.localdomain> (raw)
In-Reply-To: <20241023082852.2780488-43-huangdengdui@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/146904
_Compilation OK_
Submitter: Dengdui Huang <huangdengdui@huawei.com>
Date: Wed, 23 Oct 2024 16:28:11 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 3ee7a3e0e0e0f5a81a4b102a834697bc488fb32f
146864-146904 --> 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-10-23 8:36 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241023082852.2780488-43-huangdengdui@huawei.com>
2024-10-23 8:02 ` qemudev [this message]
2024-10-23 8:07 ` qemudev
2024-10-23 8:33 ` |SUCCESS| pw146904 " checkpatch
2024-10-23 9:26 ` 0-day Robot
2024-10-23 19:20 ` |SUCCESS| pw146864-146904 [PATCH] [v4,42/42] vdpa/sfc: use rte strer dpdklab
2024-10-23 19:34 ` dpdklab
2024-10-23 19:45 ` dpdklab
2024-10-23 20:13 ` dpdklab
2024-10-23 20:59 ` dpdklab
2024-10-23 21:24 ` dpdklab
2024-10-23 21:54 ` dpdklab
2024-10-23 23:22 ` |FAILURE| " dpdklab
2024-10-23 23:22 ` |PENDING| " dpdklab
2024-10-23 23:26 ` |FAILURE| " dpdklab
2024-10-23 23:32 ` |SUCCESS| " dpdklab
2024-10-23 23:37 ` |PENDING| " dpdklab
2024-10-23 23:42 ` |SUCCESS| " dpdklab
2024-10-23 23:57 ` dpdklab
2024-10-24 0:15 ` dpdklab
2024-10-24 1:36 ` |PENDING| " dpdklab
2024-10-24 2:01 ` |WARNING| " dpdklab
2024-10-24 2:08 ` |FAILURE| " dpdklab
2024-10-24 3:08 ` dpdklab
2024-10-24 3:35 ` |PENDING| " dpdklab
2024-10-24 3:55 ` dpdklab
2024-10-24 4:14 ` |SUCCESS| " dpdklab
2024-10-24 4:15 ` dpdklab
2024-10-24 4:49 ` |FAILURE| " dpdklab
2024-10-24 5:08 ` |SUCCESS| " dpdklab
2024-10-24 5:16 ` |WARNING| " dpdklab
2024-10-24 5:34 ` |FAILURE| " dpdklab
2024-10-24 6:36 ` |SUCCESS| " dpdklab
2024-10-24 6:37 ` dpdklab
2024-10-24 10:50 ` dpdklab
2024-10-24 11:27 ` dpdklab
2024-10-24 11:44 ` dpdklab
2024-10-24 12:21 ` dpdklab
2024-10-27 8:41 ` |FAILURE| " dpdklab
2024-10-27 9:16 ` dpdklab
2024-10-29 7:51 ` |SUCCESS| " dpdklab
2024-10-29 7:54 ` |FAILURE| " dpdklab
2024-11-02 5:45 ` dpdklab
2024-11-03 16:47 ` |SUCCESS| " 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=202410230802.49N82mt5452301@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).