From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148017-148018 [PATCH v2 2/2] eventdev: add standard aliases for telemetry commands
Date: Wed, 6 Nov 2024 23:59:13 +0800 [thread overview]
Message-ID: <202411061559.4A6FxDRb896107@localhost.localdomain> (raw)
In-Reply-To: <20241106163106.1114932-3-bruce.richardson@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148018
_Compilation OK_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Wed, 6 Nov 2024 16:31:05 +0000
DPDK git baseline: Repo:dpdk-next-eventdev
Branch: for-main
CommitID: 5b3f2f14790d803451b62c3f26b6ca05f9bb35e4
148017-148018 --> 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-06 16:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20241106163106.1114932-3-bruce.richardson@intel.com>
2024-11-06 15:59 ` qemudev [this message]
2024-11-06 16:03 ` qemudev
2024-11-06 16:32 ` |SUCCESS| pw148018 " checkpatch
2024-11-06 17:28 ` 0-day Robot
2024-11-06 17:59 ` |SUCCESS| pw148017-148018 [PATCH] [v2,2/2] eventdev: add standard al dpdklab
2024-11-06 18:01 ` |PENDING| " dpdklab
2024-11-06 18:02 ` |SUCCESS| " dpdklab
2024-11-06 18:03 ` |PENDING| " dpdklab
2024-11-06 18:05 ` dpdklab
2024-11-06 18:08 ` |SUCCESS| " dpdklab
2024-11-06 18:10 ` dpdklab
2024-11-06 18:13 ` dpdklab
2024-11-06 18:14 ` dpdklab
2024-11-06 18:17 ` dpdklab
2024-11-06 18:46 ` dpdklab
2024-11-06 18:46 ` dpdklab
2024-11-06 19:12 ` dpdklab
2024-11-06 19:16 ` dpdklab
2024-11-06 19:21 ` dpdklab
2024-11-06 19:44 ` dpdklab
2024-11-06 20:29 ` 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=202411061559.4A6FxDRb896107@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).