From: qemudev@loongson.cn
To: test-report@dpdk.org
Subject: |SUCCESS| pw138490 [PATCH] devtools: add acronyms in dictionary for commit checks
Date: Wed, 20 Mar 2024 20:18:54 +0800 [thread overview]
Message-ID: <202403201218.42KCIsqg3660309@localhost.localdomain> (raw)
In-Reply-To: <20240320124047.753573-1-ferruh.yigit@amd.com>
Test-Label: loongarch-compilation
Test-Status: SUCCESS
http://dpdk.org/patch/138490
_Compilation OK_
Submitter: Ferruh Yigit <ferruh.yigit@amd.com>
Date: Wed, 20 Mar 2024 12:40:47 +0000
DPDK git baseline: Repo:dpdk
Branch: main
CommitID: 80ecef6d1f71fcebc0a51d7cabc51f73ee142ff2
138490 --> 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-03-20 12:43 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320124047.753573-1-ferruh.yigit@amd.com>
2024-03-20 12:18 ` qemudev [this message]
2024-03-20 12:23 ` qemudev
2024-03-20 12:42 ` checkpatch
2024-03-20 13:35 ` |SUCCESS| pw138490 [PATCH] devtools: add acronyms in dictionary for dpdklab
2024-03-20 13:36 ` dpdklab
2024-03-20 13:37 ` dpdklab
2024-03-20 13:37 ` dpdklab
2024-03-20 13:37 ` dpdklab
2024-03-20 13:37 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:38 ` dpdklab
2024-03-20 13:39 ` dpdklab
2024-03-20 13:39 ` dpdklab
2024-03-20 13:39 ` dpdklab
2024-03-20 13:39 ` dpdklab
2024-03-20 13:40 ` dpdklab
2024-03-20 13:40 ` dpdklab
2024-03-20 13:40 ` dpdklab
2024-03-20 13:40 ` dpdklab
2024-03-20 13:40 ` dpdklab
2024-03-20 13:41 ` dpdklab
2024-03-20 13:41 ` dpdklab
2024-03-20 13:41 ` dpdklab
2024-03-20 13:41 ` dpdklab
2024-03-20 13:41 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:42 ` dpdklab
2024-03-20 13:43 ` dpdklab
2024-03-20 13:43 ` dpdklab
2024-03-20 13:43 ` dpdklab
2024-03-20 13:43 ` |SUCCESS| pw138490 [PATCH] devtools: add acronyms in dictionary for commit checks 0-day Robot
2024-03-20 13:43 ` |SUCCESS| pw138490 [PATCH] devtools: add acronyms in dictionary for dpdklab
2024-03-20 13:44 ` dpdklab
2024-03-20 13:44 ` dpdklab
2024-03-20 13:44 ` dpdklab
2024-03-20 13:44 ` dpdklab
2024-03-20 13:44 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:45 ` dpdklab
2024-03-20 13:46 ` dpdklab
2024-03-20 13:46 ` dpdklab
2024-03-20 13:46 ` dpdklab
2024-03-20 13:46 ` dpdklab
2024-03-20 13:46 ` dpdklab
2024-03-20 13:47 ` dpdklab
2024-03-20 13:47 ` dpdklab
2024-03-20 13:47 ` dpdklab
2024-03-20 13:47 ` dpdklab
2024-03-20 13:48 ` dpdklab
2024-03-20 13:49 ` dpdklab
2024-03-20 13:50 ` dpdklab
2024-03-20 13:53 ` dpdklab
2024-03-20 13:54 ` dpdklab
2024-03-20 13:55 ` dpdklab
2024-03-20 14:00 ` dpdklab
2024-03-20 14:27 ` dpdklab
2024-03-20 14:48 ` dpdklab
2024-03-21 7:41 ` dpdklab
2024-03-22 1:44 ` dpdklab
2024-03-22 2:20 ` 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=202403201218.42KCIsqg3660309@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).