From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw148924 [PATCH v1 1/1] usertools/devbind: fix missing active marker
Date: Fri, 29 Nov 2024 16:01:21 +0800 [thread overview]
Message-ID: <202411290801.4AT81Lb33514302@localhost.localdomain> (raw)
In-Reply-To: <1ac9c4e65e9c653bd35018057277b3dc0cc2ade2.1732722146.git.anatoly.burakov@intel.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/148924
_Compilation OK_
Submitter: Anatoly Burakov <anatoly.burakov@intel.com>
Date: Wed, 27 Nov 2024 15:42:31 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 4843aacb0d1201fef37e8a579fcd8baec4acdf98
148924 --> 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 prev parent reply other threads:[~2024-11-29 11:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ac9c4e65e9c653bd35018057277b3dc0cc2ade2.1732722146.git.anatoly.burakov@intel.com>
2024-11-27 15:43 ` checkpatch
2024-11-27 17:03 ` 0-day Robot
2024-11-27 17:38 ` |SUCCESS| pw148924 [PATCH] [v1,1/1] usertools/devbind: fix missing a dpdklab
2024-11-27 17:39 ` dpdklab
2024-11-27 17:43 ` dpdklab
2024-11-27 18:14 ` |PENDING| " dpdklab
2024-11-27 18:30 ` dpdklab
2024-11-27 18:33 ` |SUCCESS| " dpdklab
2024-11-27 19:23 ` dpdklab
2024-11-27 19:33 ` dpdklab
2024-11-27 19:35 ` |WARNING| " dpdklab
2024-11-27 19:57 ` |SUCCESS| " dpdklab
2024-11-27 20:52 ` dpdklab
2024-11-27 21:16 ` dpdklab
2024-11-27 21:41 ` dpdklab
2024-11-27 22:19 ` dpdklab
2024-11-29 8:01 ` qemudev [this message]
2024-11-29 8:01 ` |SUCCESS| pw148924 [PATCH v1 1/1] usertools/devbind: fix missing active marker qemudev
2024-11-29 10:17 ` qemudev
2024-11-29 10:18 ` qemudev
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=202411290801.4AT81Lb33514302@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).