From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw150163-150164 [PATCH v3 2/2] ethdev: fix some functions are available in the new event
Date: Fri, 17 Jan 2025 16:56:38 +0800 [thread overview]
Message-ID: <202501170856.50H8ucDs1387652@localhost.localdomain> (raw)
In-Reply-To: <20250117091210.12419-3-lihuisong@huawei.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/150164
_Compilation OK_
Submitter: Huisong Li <lihuisong@huawei.com>
Date: Fri, 17 Jan 2025 17:12:09 +0800
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 06e2856620a70000b2a28f0ea715fc247b85fd8d
150163-150164 --> 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:[~2025-01-17 9:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250117091210.12419-3-lihuisong@huawei.com>
2025-01-17 8:56 ` qemudev [this message]
2025-01-17 9:01 ` qemudev
2025-01-17 9:24 ` |SUCCESS| pw150164 " checkpatch
2025-01-17 10:24 ` 0-day Robot
2025-01-17 13:28 ` |SUCCESS| pw150163-150164 [PATCH] [v3,2/2] ethdev: fix some function dpdklab
2025-01-17 13:29 ` dpdklab
2025-01-17 13:29 ` dpdklab
2025-01-17 13:32 ` |PENDING| " dpdklab
2025-01-17 13:32 ` dpdklab
2025-01-17 13:33 ` |SUCCESS| " dpdklab
2025-01-17 13:38 ` dpdklab
2025-01-17 13:38 ` dpdklab
2025-01-17 13:41 ` dpdklab
2025-01-17 13:42 ` dpdklab
2025-01-17 14:01 ` dpdklab
2025-01-17 14:03 ` dpdklab
2025-01-17 14:10 ` dpdklab
2025-01-17 14:13 ` dpdklab
2025-01-17 14:16 ` dpdklab
2025-01-17 15:22 ` |WARNING| " dpdklab
2025-01-17 15:34 ` |SUCCESS| " dpdklab
2025-01-17 17:01 ` dpdklab
2025-01-17 17:30 ` |WARNING| " 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=202501170856.50H8ucDs1387652@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).